CONTAP-796558: SnapMirror SVM relationship fails with Unprotected FlexVol or FlexClone in Source Volume Recovery Queue
Issue
An SVM-DR relationship can fail while applying source configuration if an unprotected FlexVol or FlexClone is still in the source volume recovery queue and a baseline or rebaseline runs.
For a deleted FlexClone, snapmirror show reports a last-transfer error similar to:
Failed to apply the source Vserver configuration. Reason: Apply failed for Object: del_volume_view Method: baseline. Reason: Volume "<destination-svm>:<volume>" not found. (entry doesn't exist).
The relationship stays unhealthy, and later updates can fail the same way, until that deleted volume leaves the source recovery queue. Incremental updates that do not rebaseline continue to skip the unprotected volume. A deleted unprotected FlexVol can be placed in the destination recovery queue without failing the transfer. MetroCluster SVM-DR is not affected.
For a deleted FlexClone, snapmirror show reports a last-transfer error similar to:
Failed to apply the source Vserver configuration. Reason: Apply failed for Object: del_volume_view Method: baseline. Reason: Volume "<destination-svm>:<volume>" not found. (entry doesn't exist).
The relationship stays unhealthy, and later updates can fail the same way, until that deleted volume leaves the source recovery queue. Incremental updates that do not rebaseline continue to skip the unprotected volume. A deleted unprotected FlexVol can be placed in the destination recovery queue without failing the transfer. MetroCluster SVM-DR is not affected.
