Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

Automatic re-queue of a migration job

The sections above describe how the Migrator for Notes Worker application identifies a crash in the migration engine and returns “Migration terminated abnormally” status.  This section describes how the Migrator for Notes server re-queues the user and resulting migration status values.

If the migration worker application returns a value of “Migration terminated abnormally” or one of the RetryJobStatus codes to the Migrator for Notes server, the migration server determines if the RetryCount exceeds the MaximumRetryCount configured for the server.     

  • If the RetryCount is less than the MaximumRetryCount, the job is re-queued by creating a new migration job in the migration queue.  This job will be a high-priority job queued for the specific workstation, ensuring that it is the next job processed by that workstation.

  • If the RetryCount for a particular migration is greater or equal to the MaximumRetryCount, the migration will be left in “Migration terminated abnormally” status or the last job status.  This allows the migration administrator to determine which migrations have exceeded the maximum allowable number of automatic restarts, and indicates that the file will need additional remediation before resetting and remigrating the user.  It should be noted that the migration server will contain a history (in the form of a migrated message table) corresponding to all of the data that has been migrated up to that point. After remediation, the migration administrator can simply reset and requeue the user to continue the migration from this point, or clear previously migrated data and clear the migrated message table to restart the migration from the beginning.

  • If a migration has been automatically restarted by this process, the Notes Migrator.nsf database will only show the status of the last migration that was restarted. Consider the situation where a migration crashed, was automatically restarted, and continued to completion without further errors. The migration status in the Migrator for Notes Database will report “Migration completed successfully” even though there was a crash on the initial run.  The migration history will indicate the first migration completed with a status of “Migration terminated abnormally” status, but this may not be evident in the Notes Migrator.nsf Lotus Notes application interface.  Advanced or customized installations of the Lotus Notes application may retrieve and summarize the complete migration history for a user, but a complete migration history is not included in the default Notes Migrator.nsf application interface.

The RetryJobStatus parameter is a string list of semicolon delimited codes that will automatically be resubmitted if the job returns with that specific status code. By default, Migrator for Notes will resubmit memory exception codes #001 (Notes memory exception) and #002 (Outlook memory exception). 


In this section, we have reviewed how the Migrator for Notes Migration Worker application detects a crash of the migration engine, how the Migrator for Notes Control Center 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 Lotus 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:


Notes Folder

Outlook Destination


$Contacts or $PeopleGroupsFlat















Sent Items to OL Sent Folder (Sent Option A)

Sent Items


Custom Folders

Custom Folder


Junk E-Mail

Junk Email



Deleted Items


Journal (Notebook)



Sent Items to Custom Folder (Sent Option B)

Specified Folder or Sent Items


All Documents/Unfiled

Unfiled (may be skipped/not migrated)



Folders with names containing "Alarms", 'Rules", "$MAPI", or "Group Calendars" are skipped.




Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation