立即与支持人员聊天
与支持团队交流

Migrator for Notes 20.14 - Installation and Configuration Guide

Section 1. Introduction Section 2. Installing Binary Tree Migrator for Notes Section 3. Setting Up the Migrator for Notes Domino Database Section 4. Configuring Settings in Migrator for Notes About us Technical support resources Appendix A: Preparing for Office 365 Migrations Appendix B: Preparing for Office 365 Modern Authentication Appendix C: Creating a Migration Farm Appendix D: Securing Migrator for Notes Web Services with Windows Authentication Appendix E: Microsoft Graph Application ID Appendix F: Modern Authentication Delegation Migration Third-party Contributions

Appendix C: Creating a Migration Farm

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Migrator for Notes provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Migrator for Notes can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Migrator for Notes distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Migrator for Notes can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Migrator for Notes provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Migrator for Notes can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Migrator for Notes distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Migrator for Notes can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

Manual versus Automated Workload Distribution

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Migrator for Notes provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Migrator for Notes can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

In a typical set up, Migrator for Notes distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Migrator for Notes can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

Manual

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Migrator for Notes provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Migrator for Notes can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Migrator for Notes distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Migrator for Notes can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级