SVM Migrate stuck in migrate-abort-failed after forcefully offline of a volume
Applies to
- SVM migrate
- ONTAP 9.15.1
Issue
- One Volume initialization failed:
Transfer failed., Failed to restart a partially completed initialize transfer, the destination volume must be recreated.
- A Volume was offlined with -force in an attempt to delete the Destination volume:
DestCluster::*> volume offline -vserver SVM01 -volume vol01 -force
Warning: Forcing offline volume delefnas1w1_PLG_FAB_vault in Vserver delefnas1b1 can potentially disrupt access to files in other volumes.
Do you want to continue? {y|n}: y
Volume "SVM01:vol01" is now offline.
- However, the deletion failed due to the existing migration relationship:
DestCluster::*> volume delete -vserver SVM01 -volume vol01 -force
Error: command failed: Volume "SVM01:vol01" in Vserver "delefnas1b1" is in one or more SnapMirror relationships. You must delete the SnapMirror relationships before you can delete this volume.
- SVM Migrate status after forcefully offlining one of the destination volumes:
Status Details: Migrate operation failed. Reason: Failed to rollback the migrate operation to the transferring phase for Vserver "SVM01". Reason: SnapMirror group list control data transfers to destination volumes have failed for Vserver "SVM01". Reason: Group Update failed (Failed to complete update operation on one or more item relationships.). To view volume-specific information, use the "vserver migrate show-volume" command. To resume the Vserver migrate operation, use the "vserver migrate resume" command. To change the source Vserver configuration, use the "vserver migrate pause" command on the destination cluster, make the configuration changes on the source cluster, and then use the "vserver migrate resume" command on the destination cluster.
