Chat now with support
Chat mit Support

Migrator for Notes 20.14.2 - User Guide

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

Recovery to PST using Manual Processes

  1. Open Migrator for Notes on the Migration Control Center where the migration failed

  2. Under Mail File Migration, expand Migration and click Advanced

  3. Select the user in the Data Pane whose migration failed.

  4. Click the Clear or Reset User(s) button in the Data Pane, and select Reset User(s) from the drop-down menu

  5. Open the AWD Migration Workstation where the original migration failed

  6. Right- click on the Migrator for Notes Worker App icon located on the Task Bar, then select Exit Now to shut down the service:

  7. Right-click on the Windows Bar, then select Task Manager

  8. Close the Outlook.exe process if still running. If the CMTProxy.exe process is still running, you may also shut it down

  9. (Optional) You may restart or log-off the workstation to avoid steps 6 – 8

  10. If you restarted, verify the original workstation has restarted and the Migrator for Notes Worker App is running again.

  11. Go back to the Migration Control Center

  12. Select Migrate in the Mail File Migration -> Migration view. Select the user(s) to be migrated in the Data Pane

  13. Select the same profile as previously used for this migration

  14. Select the original workstation or a new workstation to continue the migration process where it left off; Refer to step 14 in the General Recovery procedure for more details on this step

  15. If migrating to PST, make sure the file is available to the workstation now running the process; if it is not available, then a new PST is created and you may end up with two PSTs, which is not desirable

  16. Monitor the migration as needed

  17. The migration should complete with a status of Migrated Successfully unless it encounters a new error, in which case follow the same process to recover

Appendix G: Automatic Migration Restart

Overview

Automatic Migration Restart is a process by which any abnormal termination of the Migrator for Notes engine (commonly referred to as a ‘crash’) is identified, and the migration job is automatically re-queued.  If this occurs, the migration is restarted and resumed on the next document in the message store, until either the migration completes process the message store, or the maximum number of retries has been exceeded.

Automatic Migration Restart works in conjunction with the existing migration recovery features in Migrator for Notes to resume a migration on the next document immediately after the document which caused the crash. 

Overview

Automatic Migration Restart is a process by which any abnormal termination of the Migrator for Notes engine (commonly referred to as a ‘crash’) is identified, and the migration job is automatically re-queued.  If this occurs, the migration is restarted and resumed on the next document in the message store, until either the migration completes process the message store, or the maximum number of retries has been exceeded.

Automatic Migration Restart works in conjunction with the existing migration recovery features in Migrator for Notes to resume a migration on the next document immediately after the document which caused the crash. 

Terminology

This following table lists and describes the terms commonly used when describing the automatic restart process.

Term

Description

Migrator for Notes

Migrator for Notes application environment, encompassing the server instance.

Job

A migration event. Within the context of Migrator for Notes, each migration job is a unique event.

Migration server

Refers to the system running the Migrator for Notes web services. This is the primary instance where the web server and CMT Monitor are installed.

Migrator for Notes Database (or Notes Migrator.nsf)

Used for configuring settings, managing user records, and queuing users to the migration server.  

Migration worker

An instance of the CMT_MigrationWorker.exe application running on a migration workstation. This application runs continuously on the migration workstation, polls the migration server for pending migration jobs, and initializes an instance of the migration engine (CMTProxy.exe) for each migration job.  

Migration engine (or CMTProxy)

An instance of CMTProxy.exe, which is initialized and managed by the Migration worker. CMTProxy.exe performs the actual data migration.

Crash

Abnormal termination of the migration engine, resulting in a status of “Migration terminated abnormally.”

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen