Skip to main content
NetApp Knowledge Base

CONTAP-796558: SnapMirror SVM relationship fails with Unprotected FlexVol or FlexClone in Source Volume Recovery Queue

Views:
11
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

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.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.