メインコンテンツまでスキップ

MetroCluster IP で、 MetroCluster スイッチオーバーコマンドの処理時間が 9.5 以降になるのはなぜですか。

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

すべてのとおり  

環境

  • ONTAP 9.5 以降
  • MetroCluster IP
  • スイッチオーバー

回答

  • [1]これは、ネゴシエートスイッチオーバーワークフローの直後に修復を実行するためです。
  • さらに、リモートノードは停止しなくなり、追加の手順なしでスイッチバックを実行できるようになります。
  • 詳細については、『 MetroCluster Management and Disaster Recovery Guide 』を参照してください。

:スイッチオーバープロセスに使用される時間とクライアントへの影響は変わりません。

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::>

追加情報

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.