SVM DR fails when source volumes are unprotected
Applies to
- ONTAP 9
- SnapMirror
- SVMDR
Issue
- SVM-DR replication becomes unhealthy after some of the source volumes were unprotected and the destination volumes have a clone associated with them.
We can see the below error on Snapmirror Audit logs and Snapmirror show output:
Failed to apply the source Vserver configuration. Reason: Apply failed for Object: volume Method: baseline. Reason: Failed to delete volume "Volume" because it has one or more clones.If the volume has a clone on a different Vserver, either delete the clone using the "volume delete -vserver <vserver name> -volume <volume name>" command or split the clone using the "volume clone split start -vserver <vserver name> -flexclone <volume name>" command and then retry the SnapMirror transfer operation. If a parent or child volume was moved at the source, run "volume clone show -vserver kulssnasvm01 -parent-volume Volume" to list clones, move the volume which was moved at the source, and then try the operation again. Run "volume move start -vserver <Vserver_name> -volume pdgm8 -destination-aggregate <aggregate name>" to perform the volume move operation. If a volume move was not done, initiate another SnapMirror transfer operation.Execute "snapmirror show -destination-vserver <Vserver_name> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.