Skip to main content
NetApp Knowledge Base

New volume added causes snapmirror resync to fail

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

Applies to

  • ONTAP 9
  • Snapmirror
  • SVM-DR

Issue

  • Added a new volume to the SVMDR relationship, the snapmirror resync fails:
Last Transfer Error: Failed to initialize internal database. Reason: Failed to get information for volume. Reason: entry doesn't exist.
Execute "snapmirror show -destination-vserver <vserver_name> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
  • Volume was then deleted to be able to resync the relationship

 

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.