Skip to main content
NetApp Knowledge Base

SVM DR Sync Failure sometimes

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

Applies to

  • FAS8300
  • ONTAP version 9.13.1P14
  • SVM DR (SnapMirror)

Issue

  • SVM DR sync failed with the following error in the logs:
::> snapmirror show -destination-path vserver01-dr:
 
Last Transfer Error: 
  Failed to create Snapshot copy on volume. Volume: Flex1__0001: Snapshot operation could not be completed within the timeout window.
Transfer for volume "Flex1" failed. Reason: Failed to set "snapmirror-label" or internal tag for Snapshot copy "vserverdr.2.AAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAA.2025-06-18_bbbbbb" on volume "vserver01:Flex1". (Volume cccccccc-ccccc-cccccccccc-ccccccccccccc:Flex1 does not have Snapshot copy vserverdr.2.AAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAA.2025-06-18_bbbbbb.).
Execute "snapmirror show -destination-vserver vserver01-dr -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
  • From destination snapshot Last Transfer Error:

Failed to get transfer Snapshot information from source volume "Flex1__0002". (Volume cccccccc-ccccc-cccccccccc-ccccccccccccc:Flex1__0002 does not have Snapshot copy vserverdr.1.AAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAA.2025-05-25_dddddd.

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.