Skip to main content
NetApp Knowledge Base

SVM-DR resync fails with error Snapshot copy already exists on the destination volume

  1. Last updated
  2. Save as PDF
Views:
218
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • Storage Virtual Machine Disaster Recovery (SVM DR)
  • Snapshot

Issue

  • SVM DR relationship fails to resync and is in 'broken-off' state
  • Constituent snapmirror relationship of that SVM DR is in 'broken-off' state
  • In SNAPMIRROR.XML the SVM DR relationship has Last Transer Type 'resync' and  Last Transfer Error:

Transfer for volume "dest_vol" failed. Reason: A Snapshot copy with the name "snapshotName" already exists on destination volume "dest_svm:dest_vol". Execute "snapmirror show -destination-vserver dest_svm -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.

  • Snapshot mentioned in Last Transfer Error has 'sm' owner type

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.