Skip to main content
NetApp Knowledge Base

Why does the MetroCluster Switchover command take longer in 9.5 and later on a MetroCluster IP?

  1. Last updated
  2. Save as PDF
Views:
550
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

​ ​ ​  

Applies to

  • ONTAP 9.5 and later
  • MetroCluster IP
  • Switchover

Answer

  • This is due to executing healing directly after negotiated switchover workflow.
  • In addition, the remote nodes will no longer halt and a switchback can be executed without any additional steps.
  • More information can be found in the MetroCluster management and disaster recovery guide.

Note: The time used for the switchover process itself as well as the client impact remains unchanged.

ClusterA::> metrocluster  switchover

Warning: negotiated switchover is about to start. It will stop all the data
         Vservers on cluster "ClusterB" and automatically restart them on
         cluster "ClusterA".
Do you want to continue? {y|n}: y

[Job 669] Job is queued: MetroCluster Negotiated Switchover Job.               
[Job 669] Preparing the cluster for the switchover operation...                
[Job 669] Synchronizing cluster configuration from the remote cluster (attempt 1 of 30).[Job 669]
Job succeeded: Switchover is successful.
MetroCluster Auto Heal Job is running. Job ID is 670
Heal aggregates phase is in progress.                                          
Preparing for the heal root aggregates phase.                                  
Heal root aggregates phase is in progress.                                    
MetroCluster auto heal completed successfully.
ClusterA::>

Additional Information

additionalInformation_text

 

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.