This article describes the common causes of migration errors and appropriate actions to be taken to resolve them.

Migration Status "IN ERROR"

When one or more volumes within a migration session encounter migration error, the migration session will become in error. Once a migration volume is in error, synchronization will be suspended after appropriate retry attempts. However, unlike a "migration failed" status, synchronization progress is preserved when a session is in error.

Once the error condition is cleared, you can trigger another synchronization attempt by clicking on Trigger Synchronization in the migration session action menu.

Cause of Migration Error

When a migration session in error, you can find the reason of the error under every migration volumes that is in error.

Migration Error Reason

Common Migration Errors

The following is a list of common migration session error reasons and the suggested troubleshooting actions.

If the suggested actions have already been taken and the migration errors persist, please contact support.

Out of Memory
Some of the migration process cannot allocate sufficient memory to complete the tasks. Validate the system memory usage. If error is caused by sudden spike of memory usage, you can safely retry the operation.

Resource Busy
Storage volume is busy and the long response time from storage affected migration operations. You can safely retry synchronization when the storage volumes are not overloaded.

Operation Timed Out
Internal CMC operation could not complete within timeout. This could be due to network delays or overall high CPU/Memory consumption. You are safe to retry the operation.

Operation Cancelled
The migration operation was cancelled because the host was restarted. The sessions in error can be recovered by triggering session synchronization.

Device Unavailable
One or more storage volumes being migrated are not ready in the system. This is possibly due to the volumes require more time to be connected, e.g., iSCSI volumes. The sessions involved are put in error. The sessions in error can be recovered by triggering session resynchronization.

Autonomous Triggered
Autonomous mode has been triggered on the source volume to ensure production IO is not interrupted. This may be just a temporary condition. The sessions involved are put in error. The sessions in error can be recovered by triggering session resynchronization.

Device I/O Error
I/O error encountered when I/O commands are executed to the storage volumes. Check the device operational condition to ensure it is normal.

Fatal
Fatal error encountered in migration operation. Please contact support.
Was this article helpful?
Cancel
Thank you!