Skip to main content
NetApp Knowledge Base

Conversion of DP Mirrors to a SVM DR relationship fails during resync, indicating there are one or more volumes that do not have a SnapMirror relationship

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

Applies to

  • 9.1P14 CLUSTER-MODE
  • SnapMirror
  • SVM-DR

Issue

  • When running a SnapMirror resync for an SVM DR to complete the conversion from individual DP Mirrors, the following occurs:


destinationcluster::>snapmirror resync -destination-path destination_vserver_name:
Error: command failed: There are one or more volumes in this Vserver which do not have a volume-level SnapMirror relationship with volumes in Vserver "destination_vserver_name".

When running a SnapMirror resync for an SVM-DR to complete the conversion from the single volume SnapMirrors, the following error occurs:
"Error: command failed: There are one or more volumes in this Vserver which do not have a volume-level SnapMirror relationship with volumes in Vserver [destination_vserver_name]"

  • When the number of relationships between the source and destination is accounted for, it is found to match the number of volumes on both the source and destination vservers.

 

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.