5. Return the controller to normal operation:
If your system is in… Issue this command from the partner’s console…
An HA pair
storage failover giveback -ofnode impaired_node_name
A two-node MetroCluster
configuration
Proceed to the next step. The MetroCluster switchback procedure is done in
the next task in the replacement process.
6.
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto
-giveback true
Step 5 (two-node MetroCluster only): Switch back aggregate
After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the
MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-
source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the
local disk pools.
This task only applies to two-node MetroCluster configurations.
Steps
1.
Verify that all nodes are in the
enabled state: metrocluster node show
cluster_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.
2.
Verify that resynchronization is complete on all SVMs:
metrocluster vserver show
3. Verify that any automatic LIF migrations being performed by the healing operations were completed
successfully:
metrocluster check lif show
4.
Perform the switchback by using the
metrocluster switchback command from any node in the
surviving cluster.
5.
Verify that the switchback operation has completed:
metrocluster show
The switchback operation is still running when a cluster is in the waiting-for-switchback state:
412
To Next Page
Loading...
