Skip to main content
NetApp Knowledge Base

SVM DR resync or update failed by "Failed to initialize internal database" error

  1. Last updated
  2. Save as PDF
Views:
3,056
Visibility:
Public
Votes:
1
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • SVM DR

Issue

Resync or update of SVM DR relationship fails by following error:

Failed to initialize internal database. Reason: Failed to get information for volume. Reason: entry doesn't exist. Check whether the 'vserver-dr-protection' attribute matches for volumes at the source and the destination vserver.
Execute "snapmirror show -destination-vserver <DESTINATION_SVM> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.

Note: Configuration change or manual update of vserver-dr-protection attribute on source volume can cause this error

 

 

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.