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” |
Configuring Automatic Restart
Automatic restart is controlled by a parameter in the Web.config file for the Migrator for Notes server. This file is located in [installDirectory]\CMT for Exchange\CMT_XMLServer\Web.config , for example “C:\Program Files (x86)\BinaryTree\CMT for Exchange\CMT_XMLServer\web.config”.
The Web.config file contains the startup parameters for the Migrator for Notes Server. Located in this file is an \appSettings\MaximimumRetryCount XML node, which indicates the maximum number of times a migration will be automatically restarted.
<appSettings>
---snip ----
<add key="ScheduleTimerInterval" value="3"></add>
<add key="UseSQL" value="1"></add>
<add key="MaximumRetryCount" value="10"></add>
<add key="RetryJobStatus" value="#001;#002"></add>
</appSettings>
The MaximumRetryCount is set to 10 by default. A value of 0 or a negative number will disable the Automatic Restart functionality.
RetryJobStatus is set by default to resubmit if the #001 (Notes memory exception) or #002 (Outlook memory exception) job status code is returned.
|
|
If the MaximumRetryCount is changed or disabled, the Migrator for Notes Server instance must be restarted for the change to take effect. This can be done by opening a command prompt on the migration server and typing “iisreset” at the prompt, or manually restarting the IIS service. |
|
|
Windows Error Reporting can prevent the Migration Worker from completing the Automatic Restart. This can be disabled on Windows using Disable-WindowsErrorReporting, for more information please refer to Microsoft Online Documentation for this functionality. |
