Skip to main content
NetApp Knowledge Base

SVMDR resync fails with error Volume is not initialized

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

Applies to

  • ONTAP 9
  • SVMDR

Issue

  • In an existing SVM DR relationship, type DP with identity preserve false, a new volume is added on the source end and the destination is updated creating a new volume on DR site.
  • After breaking the SVM DR relationship, the DR volume fails to resync with the following error:

Transfer for volume "Vol_dr" failed. Reason: Volume svm2:Vol_dr is not initialized.

From SnapMirror_Audit.log

Sat Sep 24 17:20:02 IST 2022 ResyncSetup[Sep 24 17:20:02]:164e0a55-39be-11ed-a609-d039ea425527 Operation-Uuid=0656e861-3bff-11ed-a609-d039ea425527 Group=vserver Operation-Cookie=7146912270180680452 action=End source=SVM1:Vol_sr destination=svm2:Vol_dr status=Failure message=Volume svm2:Vol_dr is not initialized.

From EMS-LOG-FILE.txt

[wafl.mirror.access.denied:warning] Access to SnapMirror volume Vol_dr was denied because SnapMirror initialization was not complete (exported Snapshot copy identifier '0' is invalid).

 

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.