Skip to main content
NetApp Knowledge Base

Unhealthy SVMDR Status After Source Volume Deletion

  1. Last updated
    Jan 2, 2025
  2. Save as PDF
Views:
42
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:
1/2/2025, 10:20:57 AM

Applies to

  • ONTAP 9
  • SnapMirror
  • SnapMirror cascade
  • SVMDR
  • BlueXP

Issue

  • SVMDR replication may become unhealthy after the deletion of a source volume involved in an SVMDR relationship.
  • The following errors are encountered:

"Failed to apply the source Vserver configuration. Reason: Volume 'vol1' in Vserver 'svm1' is the destination or source endpoint of one or more SnapMirror relationships. Before deleting the volume, delete the relationships for which it is the destination endpoint, and release the source information for relationships for which it is the source endpoint using 'snapmirror release'."

"Failed to apply the source Vserver configuration. Reason: Apply failed for Object: volume Method: baseline. Reason: Volume 'vol1' in Vserver 'svm1' is the destination or source endpoint of one or more SnapMirror relationships. Before deleting the volume, delete the relationships for which it is the destination endpoint, and release the source information for relationships for which it is the source endpoint using 'snapmirror release'.

 

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.