Skip to main content
NetApp Knowledge Base

SVM-DR The latest Snapshot copy on the destination is not the base Snapshot copy

Views:
906
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SVM-DR
  • SnapMirror

Issue

SVM-DR update fails with error:

Transfer for volume "Vol_Name" failed. Reason: The latest Snapshot copy "vserverdr_Snapshot_Name" on the destination is not the base Snapshot copy. Use the "snapmirror resync" command to correct the issue.
 
Execute "snapmirror show -destination-vserver SVM_Name -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
 
Upon expanding, you see the below last trasfer error on the constituent volume:-
 
The latest Snapshot copy "vserverdr_Snapshot_Name" on the destination is not the base Snapshot copy. Use the "snapmirror resync" command to correct the issue. 
  • When a SnapMirror relationship is updated (either manually or via a schedule) a new snapshot is created on the Source volume.
  • This snapshot is the most recent snapshot in the volume and will be used as a base snapshot for the transfer. 

 

 

 

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.