Switch back aggregates in a two-node MetroCluster configuration - AFF A300
This task only applies to two-node MetroCluster configurations.
-
Verify that all nodes are in the
enabledstate:metrocluster node showcluster_B::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- 1 cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. -
Verify that resynchronization is complete on all SVMs:
metrocluster vserver show -
Verify that any automatic LIF migrations being performed by the healing operations were completed successfully:
metrocluster check lif show -
Perform the switchback by using the
metrocluster switchbackcommand from any node in the surviving cluster. -
Verify that the switchback operation has completed:
metrocluster showThe switchback operation is still running when a cluster is in the
waiting-for-switchbackstate:cluster_B::> metrocluster show Cluster Configuration State Mode -------------------- ------------------- --------- Local: cluster_B configured switchover Remote: cluster_A configured waiting-for-switchback
The switchback operation is complete when the clusters are in the
normalstate.:cluster_B::> metrocluster show Cluster Configuration State Mode -------------------- ------------------- --------- Local: cluster_B configured normal Remote: cluster_A configured normal
If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using the
metrocluster config-replication resync-status showcommand. -
Reestablish any SnapMirror or SnapVault configurations.