Skip to main content
NetApp Knowledge Base

vserver status of pending-setup after maintenance

Views:
54
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • Vserver migration using SVM DR

Issue

After a successful SVM DR migration to a MetroCluster, the configuration is not replicated to the remote cluster and the affected vserver is shown in a non-healthy state

 
Example:
Cluster1::> metrocluster vserver show -vserver vserver1

Cluster: Cluster1
                            Partner                       Configuration
Vserver                     Vserver                       State
-------------------         ----------------------        -----------------
vserver1                    -                             pending-setup
  Corrective Action: Vserver with the same name exists on the partner
            cluster. To fix the problem, rename the Vserver "vserver1".

On the DR site:

Cluster2::> metrocluster vserver show

Cluster: Cluster2
                            Partner                       Configuration
Vserver                     Vserver                       State
-------------------         ----------------------        -----------------
...
vserver1                    vserver1-mc                   unhealthy
...

 

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.