These are migration status' you may see in the Notes Migration.nsf UI
• Pending - This status means a migration worker has picked up the job, but the actual migration has not started
• In Progress - This status means a migration worker is actively migrating the source data to it's destination
• Requeued: Retry... - This status means there was an issue with the migration, possibly due to a worker crash. Notes Migrator will retry the migration, skipping the document it crashed on.
• 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.
• 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 user migration.
• Not Queued: Migration history is pending update – The migration was not started due to the history of a previous migration not being updated.
• Migration initialization failed (Version 4.x and earlier, removed from 5.0) - This status can occur if the migration account does not have access to the source or destination mailbox (or one doesn't exist).
New to version 5.0
• Migration failed: Exchange is not available – The migration failed because Exchange was not available.
• Nothing in Source File – The source mail file is able to open but does not contain any data .
• Source Database Not Initialized – The source mail file fails to open with “Database Not Initialized”. This status can occur if the migration account does not have access to the source mailbox (or one doesn't exist), or the staging replica stub has not had a chance to complete it's replication.
• AutoDiscover Failure – The Target mailbox fails to connect with Autodiscover .
© ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center