SVM DR initialize, resync or update fails with error: Failed to start transfer
Applies to
- Ontap 9.10
- SnapMirror Storage Virtual Machine Disaster Recovery (SVM DR)
Issue
- SVM DR fails to initialize, resync, or update for one or many volumes.
- The error message can be one of the following:
Failed to apply the source Vserver configuration. Reason: Failed to enable efficiency on volume "<Vol_Name>" of Vserver "<Vserver_name>": A SnapMirror transfer is running or paused. Use the "snapmirror show" command to view the status of the transfer. Retry this command when the transfer is complete, or run "snapmirror abort -hard true" to abort the SnapMirror transfer and clear any checkpoint data.
Transfer for volume <Vol_Name> failed. Reason: Failed to start transfer for Snapshot copy "<snapname>". (Failed to start transfer. (Duplicate transfer specified (Replication engine error))).
Execute "snapmirror show -destination-vserver <vserver> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
Transfer for volume "<Vol_Name>" failed. Reason: Failed to start transfer for Snapshot copy "<snapname>". (Failed to start transfer. (Duplicate transfer specified (Replication engine error))).
Execute "snapmirror show -destination-vserver bpcifs1002_dr -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.