Skip to main content
NetApp Knowledge Base

SVM DR indicates "source cluster does not have eligible SVMs to protect"

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

Applies to

  • SVM DR
  • ONTAP 9.5 and earlier
  • A peered cluster intended for SVM DR is configured with FabricPool Aggregates

Issue

  • When attempting to replicate SVM configuration using OnCommand System Manager, the SVM DR initialize fails with The source cluster does not have eligible SVMs to protect
  • SnapMirror of individual volumes is possible between the peered clusters, but SVM DR cannot be configured
  • From the ONTAP CLI on the destination, if snapmirror show  is used to obtain more information about the problem, we see Metadata volume is not available and a reference to the source cluster.

dr_clust::> snapmirror show -destination-vserver CIFS_DR -fields last-transfer-error,unhealthy-reason -expand

Metadata volume is not available on cluster "source". Run "snapmirror config-replication status show" for more details. Execute "snapmirror show -destination-vserver CIFS_DR -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors. Transfer failed

 

 

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.