Skip to main content
NetApp Knowledge Base

SnapMirror resync fails with error "Reason: Failed to set exported Snapshot copy ... (The snapshot name does not exist)..."

Views:
1,819
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
DP
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • SVM-DR

Issue

  • SnapMirror resync operation fails with “Failed to set exported Snapshot copy” as below.

Example:

Cluster::> snapmirror resync -destination-path DS_SVM_DR:
Cluster::> snapmirror show
                                                                                 Progress
Source         Destination  Mirror      Relationship    Total                    Last
Path     Type  Path         State       Status          Progress   Healthy       Updated
-------  ----  ----------   -------     --------------  ---------  -------       --------
SC_SVM:  XDP   DS_SVM_DR:   Broken-off  Transferring    -          false         -
 
Cluster::> snapmirror show -destination-path DS_SVM_DR: 

        Source Path: SC_SVM_DR: 
   Destination Path: DS_SVM_DR:
            Healthy: false
   Unhealthy Reason: Transfer failed.
 Last Transfer Type: resync
Last Transfer Error: Transfer for volume "DS_Vol1" failed. Reason: Failed to set exported Snapshot copy vserverdr.0.UUID.DATE on volume DS_SVM_DR:DS_vol1. (The snapshot name does not exist).

 

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.