지금 지원 담당자와 채팅
지원 담당자와 채팅

Binary Tree Migrator for Notes 20.12.1 - User Guide for Office 365

Section 1. Introduction Section 2. Pre-migration Activities Section 3. User Provisioning Section 4. Email Repliability Section 5. Migrating Mail Files Section 6. Rooms and Resources Database Migration Section 7. Mail-in Database Migration Section 8. Setting Migration Status Section 9. Access and Delegation Migration Section 10. All Accounts Section 11. Customer Status Reports Section 12. Logs About us Technical support resources Appendix A: Staging Replicas Appendix B: Pre-Migration Troubleshooting Appendix C: Work with Files (Import/Export) Appendix D: Item Processing Results Appendix E: Migration Result Statuses Appendix F: Recovery Process Appendix G: Automatic Migration Restart Appendix H: Folder Processing Order

Set Migration Workstation

The following results are returned to the migration controller server for the overall migration status of all items:

  • Migrated Successfully – Completed processing all items, no problems during initialization, no critical errors encountered.  There may be non-critical Warnings, Errors or failures during individual document processing, but these do not stop the migration.  The migration will still be considered successful even if there are document warnings or errors.

  • Migration Failed – Critical errors/failures encountered that prevent the migration from continuing/completing.  This status is typically caused by network/server connectivity problems.

  • Terminated Abnormally – This status is set by the migration worker when CMTProxy.exe (migration engine) crashes; this is typically caused by corrupt source data, a Notes client crash or Exchange terminating the migration connection

  • Failed to Initialize – Incorrect/Incompatible configuration settings, missing configuration or reference files, failure to connect to source or destination servers, and so on.  No data is migrated

  • Migration cancelled – Manual cancellation of the migration the user

  • Not Queued: Migration history is pending update – The migration was not started due to the history of a previous migration not being updated

  • Migration failed: Exchange is not available – The migration failed because Exchange was not available

  • Nothing in Source File – The source mailfile is able to open but does not contain any data

  • Source Database Not Initialized – The source mailfile fails to open with “Database Not Initialized”

  • AutoDiscover Failure – The Target mailbox fails to connect with Autodiscover

     

 


Additional details for a migration can be viewed in the migration log.

    


A migration of an account can be marked as Migrated Successfully but have non-critical errors for individual source Notes documents items. The individual items with errors will not necessarily have migrated correctly. If there are errors recorded during a successful migration the error count will be shown in the Migrator for Notes Migration views. These can be checked in the Migration Log for the account and verified. For example, the end user did not decrypt source Notes messages or a source Notes document did not have all expected field data. In these cases, the migration is considered as successful as the source data for individual documents could not be processed but the migration was not aborted by either Notes or Outlook. Re-migrating the account could potentially resolve these errors. In cases where specific details are required a migration profile with Verbose logging enabled should be used to re-migrate an account.

 

Set Migration Status

To manually update the status of migrated items, follow the steps below.

  1. Expand the Migration | Advanced view; select rooms and resources in the Data Pane

  2. At the top menu, click Actions | Other; the Run Agent dialog box will open

  3. Select Set Migration Status and click Run:

  4. From the Set Migration Status dialog box, then, for example, select Ready to Process and click OK:

  5. A status message box displays showing that the migration status will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

Set Migration Group

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Group in the dialog box and click Run:

  3. Specify the migration group name in the Migration Group dialog box and click OK:

  1. A status message box displays showing that the migration group will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Workstation in the dialog box and click Run:

 

  1. From the Set Migration Workstation dialog box, select a workstation on which to run the selected users’ migrations, and then click OK:

  2. A confirmation box appears; click Yes to confirm that you want the selected migration workstation to be set for selected rooms and resources

  3. A status message box displays showing that the migration workstation will be set for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status

Clear Migration Status

  1. In the same way, you can clear set migration status, migration group, and migration workstation by selecting appropriate options; if you do not set the migration workstation manually, Migrator for Notes will automatically farm the migration job out to the next available worker in the migration farm

  2. Select the rooms and the resources, then click the Additional Actions button to display its drop-down menu options:

    The drop-down menu options are as follows:

Option

Description

Clear Selected DB(s) and re-populate

Selected room or resource will be cleared and then repopulated to import the updated information

Delete Selected DB(s)

Selected room or resource will be deleted from the Migrator for Notes database as well as the database into which the rooms or resources schedule was exported

 

  1. After you have performed all the pre-migration actions on the rooms and resources, go back to the Migrate view

  2. Select all the rooms and resources you wish to migrate then click the Migrate Rooms & Resources button in the Data Pane toolbar

  3. The Select Migration Priority dialog box appears; click OK to trigger the migration:

    Depending on the size of the data being migrated, the transfer may take from few minutes to several minutes

  4. The Refresh Migration Status button allows you to refresh the status of the selected rooms and resources

     

Set Migration MCC

In some cases, you have the option to set the Migration MCC. Refer to the chart below for a description of these MCC options:


This option should only be used in cases where more than 120 migration workers are required and an additional migration control center server cannot be deployed.

 

Option

Description

Set Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled on the Migrator for Notes Settings | Other Settings | Enable Advanced Features

 

Allows you to manually assign a Migration Control Centers (MCC) to process an item’s data

Clear Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled; Allows you to clear the Migration MCC assigned to item(s)

 

Clear Migration Status

The following results are returned to the migration controller server for the overall migration status of all items:

  • Migrated Successfully – Completed processing all items, no problems during initialization, no critical errors encountered.  There may be non-critical Warnings, Errors or failures during individual document processing, but these do not stop the migration.  The migration will still be considered successful even if there are document warnings or errors.

  • Migration Failed – Critical errors/failures encountered that prevent the migration from continuing/completing.  This status is typically caused by network/server connectivity problems.

  • Terminated Abnormally – This status is set by the migration worker when CMTProxy.exe (migration engine) crashes; this is typically caused by corrupt source data, a Notes client crash or Exchange terminating the migration connection

  • Failed to Initialize – Incorrect/Incompatible configuration settings, missing configuration or reference files, failure to connect to source or destination servers, and so on.  No data is migrated

  • Migration cancelled – Manual cancellation of the migration the user

  • Not Queued: Migration history is pending update – The migration was not started due to the history of a previous migration not being updated

  • Migration failed: Exchange is not available – The migration failed because Exchange was not available

  • Nothing in Source File – The source mailfile is able to open but does not contain any data

  • Source Database Not Initialized – The source mailfile fails to open with “Database Not Initialized”

  • AutoDiscover Failure – The Target mailbox fails to connect with Autodiscover

     

 


Additional details for a migration can be viewed in the migration log.

    


A migration of an account can be marked as Migrated Successfully but have non-critical errors for individual source Notes documents items. The individual items with errors will not necessarily have migrated correctly. If there are errors recorded during a successful migration the error count will be shown in the Migrator for Notes Migration views. These can be checked in the Migration Log for the account and verified. For example, the end user did not decrypt source Notes messages or a source Notes document did not have all expected field data. In these cases, the migration is considered as successful as the source data for individual documents could not be processed but the migration was not aborted by either Notes or Outlook. Re-migrating the account could potentially resolve these errors. In cases where specific details are required a migration profile with Verbose logging enabled should be used to re-migrate an account.

 

Set Migration Status

To manually update the status of migrated items, follow the steps below.

  1. Expand the Migration | Advanced view; select rooms and resources in the Data Pane

  2. At the top menu, click Actions | Other; the Run Agent dialog box will open

  3. Select Set Migration Status and click Run:

  4. From the Set Migration Status dialog box, then, for example, select Ready to Process and click OK:

  5. A status message box displays showing that the migration status will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

Set Migration Group

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Group in the dialog box and click Run:

  3. Specify the migration group name in the Migration Group dialog box and click OK:

  1. A status message box displays showing that the migration group will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

Set Migration Workstation

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Workstation in the dialog box and click Run:

 

  1. From the Set Migration Workstation dialog box, select a workstation on which to run the selected users’ migrations, and then click OK:

  2. A confirmation box appears; click Yes to confirm that you want the selected migration workstation to be set for selected rooms and resources

  3. A status message box displays showing that the migration workstation will be set for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status

  1. In the same way, you can clear set migration status, migration group, and migration workstation by selecting appropriate options; if you do not set the migration workstation manually, Migrator for Notes will automatically farm the migration job out to the next available worker in the migration farm

  2. Select the rooms and the resources, then click the Additional Actions button to display its drop-down menu options:

    The drop-down menu options are as follows:

Option

Description

Clear Selected DB(s) and re-populate

Selected room or resource will be cleared and then repopulated to import the updated information

Delete Selected DB(s)

Selected room or resource will be deleted from the Migrator for Notes database as well as the database into which the rooms or resources schedule was exported

 

  1. After you have performed all the pre-migration actions on the rooms and resources, go back to the Migrate view

  2. Select all the rooms and resources you wish to migrate then click the Migrate Rooms & Resources button in the Data Pane toolbar

  3. The Select Migration Priority dialog box appears; click OK to trigger the migration:

    Depending on the size of the data being migrated, the transfer may take from few minutes to several minutes

  4. The Refresh Migration Status button allows you to refresh the status of the selected rooms and resources

     

Set Migration MCC

In some cases, you have the option to set the Migration MCC. Refer to the chart below for a description of these MCC options:


This option should only be used in cases where more than 120 migration workers are required and an additional migration control center server cannot be deployed.

 

Option

Description

Set Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled on the Migrator for Notes Settings | Other Settings | Enable Advanced Features

 

Allows you to manually assign a Migration Control Centers (MCC) to process an item’s data

Clear Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled; Allows you to clear the Migration MCC assigned to item(s)

 

Set Migration MCC

The following results are returned to the migration controller server for the overall migration status of all items:

  • Migrated Successfully – Completed processing all items, no problems during initialization, no critical errors encountered.  There may be non-critical Warnings, Errors or failures during individual document processing, but these do not stop the migration.  The migration will still be considered successful even if there are document warnings or errors.

  • Migration Failed – Critical errors/failures encountered that prevent the migration from continuing/completing.  This status is typically caused by network/server connectivity problems.

  • Terminated Abnormally – This status is set by the migration worker when CMTProxy.exe (migration engine) crashes; this is typically caused by corrupt source data, a Notes client crash or Exchange terminating the migration connection

  • Failed to Initialize – Incorrect/Incompatible configuration settings, missing configuration or reference files, failure to connect to source or destination servers, and so on.  No data is migrated

  • Migration cancelled – Manual cancellation of the migration the user

  • Not Queued: Migration history is pending update – The migration was not started due to the history of a previous migration not being updated

  • Migration failed: Exchange is not available – The migration failed because Exchange was not available

  • Nothing in Source File – The source mailfile is able to open but does not contain any data

  • Source Database Not Initialized – The source mailfile fails to open with “Database Not Initialized”

  • AutoDiscover Failure – The Target mailbox fails to connect with Autodiscover

     

 


Additional details for a migration can be viewed in the migration log.

    


A migration of an account can be marked as Migrated Successfully but have non-critical errors for individual source Notes documents items. The individual items with errors will not necessarily have migrated correctly. If there are errors recorded during a successful migration the error count will be shown in the Migrator for Notes Migration views. These can be checked in the Migration Log for the account and verified. For example, the end user did not decrypt source Notes messages or a source Notes document did not have all expected field data. In these cases, the migration is considered as successful as the source data for individual documents could not be processed but the migration was not aborted by either Notes or Outlook. Re-migrating the account could potentially resolve these errors. In cases where specific details are required a migration profile with Verbose logging enabled should be used to re-migrate an account.

 

Set Migration Status

To manually update the status of migrated items, follow the steps below.

  1. Expand the Migration | Advanced view; select rooms and resources in the Data Pane

  2. At the top menu, click Actions | Other; the Run Agent dialog box will open

  3. Select Set Migration Status and click Run:

  4. From the Set Migration Status dialog box, then, for example, select Ready to Process and click OK:

  5. A status message box displays showing that the migration status will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

Set Migration Group

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Group in the dialog box and click Run:

  3. Specify the migration group name in the Migration Group dialog box and click OK:

  1. A status message box displays showing that the migration group will be changed for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status:

Set Migration Workstation

  1. At the top menu, click Actions | Other; the Run Agent dialog box will open

  2. Select Set Migration Workstation in the dialog box and click Run:

 

  1. From the Set Migration Workstation dialog box, select a workstation on which to run the selected users’ migrations, and then click OK:

  2. A confirmation box appears; click Yes to confirm that you want the selected migration workstation to be set for selected rooms and resources

  3. A status message box displays showing that the migration workstation will be set for the selected rooms; click Yes to confirm

    Notice that the selected rooms and resources are now listed under the applied status

Clear Migration Status

  1. In the same way, you can clear set migration status, migration group, and migration workstation by selecting appropriate options; if you do not set the migration workstation manually, Migrator for Notes will automatically farm the migration job out to the next available worker in the migration farm

  2. Select the rooms and the resources, then click the Additional Actions button to display its drop-down menu options:

    The drop-down menu options are as follows:

Option

Description

Clear Selected DB(s) and re-populate

Selected room or resource will be cleared and then repopulated to import the updated information

Delete Selected DB(s)

Selected room or resource will be deleted from the Migrator for Notes database as well as the database into which the rooms or resources schedule was exported

 

  1. After you have performed all the pre-migration actions on the rooms and resources, go back to the Migrate view

  2. Select all the rooms and resources you wish to migrate then click the Migrate Rooms & Resources button in the Data Pane toolbar

  3. The Select Migration Priority dialog box appears; click OK to trigger the migration:

    Depending on the size of the data being migrated, the transfer may take from few minutes to several minutes

  4. The Refresh Migration Status button allows you to refresh the status of the selected rooms and resources

     

In some cases, you have the option to set the Migration MCC. Refer to the chart below for a description of these MCC options:


This option should only be used in cases where more than 120 migration workers are required and an additional migration control center server cannot be deployed.

 

Option

Description

Set Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled on the Migrator for Notes Settings | Other Settings | Enable Advanced Features

 

Allows you to manually assign a Migration Control Centers (MCC) to process an item’s data

Clear Migration MCC

Appears only if multiple Migration Control Centers (MCCs) are enabled; Allows you to clear the Migration MCC assigned to item(s)

 

Appendix F: Recovery Process

The Migrator for Notes migration engine has been enhanced to track the status of processed messages during migration to help recover failed migrations.

If a critical failure occurs in the migration engine, the migration process can terminate unexpectedly. The user status must be reported in Notes Migrator.nsf as “Migration terminated abnormally.” After correcting the cause of the failure, the new recovery feature allows Migrator for Notes users to restart migrating to an Exchange mail store or to a PST file from the point of crash. It prevents the application from reprocessing messages that were migrated during the initial run of the migration and moves to the next message in the message store without attempting to reprocess the message that caused the failure.

In addition, this feature also allows Migrator for Notes users to restart the migration on a secondary workstation if the first workstation is now busy after the original failed status.

In cases where a failure is caused by API errors processing the data, from Notes using the HCL Notes API or into Outlook using the MAPI API, the source document reference (UNID) will be marked in the migration history as a bad document. These types of faults are typically caused by memory exception errors as a result of source data that the vendor's API cannot process.

Subsequent migrations will skip processing (not migrate) a source document that caused a memory exception error where the migration worker was able to obtain the document UNID.

This section outlines the common reasons for a failed migration and recovery processes for each possible scenario and provides a background to the implementation and usage of this new feature.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택