Migrator for Notes 20.14.2 - User Guide for Office 365

Summary

In this section, we have reviewed how the Notes Migrator Migration Worker application detects a crash of the migration engine, how the Migrator for Notes server processes the “Migration Terminated Abnormally” status and requeues the job if necessary, and ultimately how the migration automatically restarts on the same workstation.

In this manner, the Automatic Restart process in Migrator for Notes allows migration administrators to queue jobs to the migration server and know that if a crash were to occur the migration will automatically be restarted without intervention up to the maximum number of times indicated by the MaximumRetryCount parameter.  This feature reduces the amount of resources required to monitor Migrator for Notes migrations and eliminates the need for administrator intervention in the case where the migration engine has crashed.

Again, it should be noted that the HCL Notes application interface (Notes Migrator.nsf) will report the last migration status for the user.  Any automatic restart events will be evident in the complete migration history but will not be reflected directly in the interface.  In the case where the maximum restart count has been exceeded, the last migration event will be reported as “Migration terminated abnormally.”

Appendix H: Folder Processing Order

Folders are processed in the following order: