Healing and switching back aggregates in a two-node MetroCluster configuration

After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster healing and switchback operations. These operations return 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.

About this task

This task only applies to two-node MetroCluster configurations.

Steps

  1. Resynchronize the aggregates by using the metrocluster heal -phase aggregates command from the surviving cluster.
    Example
    controller_A_1::> metrocluster heal -phase aggregates 
    [Job 130] Job succeeded: Heal Aggregates is successful.
    

    If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.

  2. Verify that the operation was completed successfully by using the metrocluster operation show command.
    Example
    controller_A_1::> metrocluster operation show
        Operation: heal-aggregates
          State: successful
    Start Time: 7/25/2014 18:45:55
       End Time: 7/25/2014 18:45:56
         Errors: -
    
  3. Check the state of the aggregates by using the storage aggregate show command.
    Example
    controller_A_1::> storage aggregate show
    Aggregate     Size Available Used% State   #Vols  Nodes            RAID Status
    --------- -------- --------- ----- ------- ------ ---------------- ------------
    ...
    aggr_b2    227.1GB   227.1GB    0% online       0 mcc1-a2          raid_dp, mirrored, normal...
  4. Switch back the mirrored aggregates by using the metrocluster heal -phase root-aggregates command.
    Example
    mcc1A::> metrocluster heal -phase root-aggregates
    [Job 137] Job succeeded: Heal Root Aggregates is successful
    

    If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.

  5. Verify that the heal operation was completed successfully by using the metrocluster operation show command on the healthy cluster:
    Example
    mcc1A::> metrocluster operation show
      Operation: heal-root-aggregates
          State: successful
     Start Time: 7/29/2014 20:54:41
       End Time: 7/29/2014 20:54:42
         Errors: -
    
    
  6. Verify that all nodes are in the enabled state: metrocluster node show
    Example
    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
                  controller_A_2 configured     enabled   heal roots completed
          cluster_B
                  controller_B_1 configured     enabled   waiting for switchback recovery
                  controller_B_2 configured     enabled   waiting for switchback recovery
    4 entries were displayed.
    
  7. Verify that resynchronization is complete on all SVMs: metrocluster vserver show
  8. Verify that any automatic LIF migrations being performed by the healing operations were completed successfully: metrocluster check lif show
  9. Perform the switchback by using the metrocluster switchback command from any node in the surviving cluster.
  10. Verify that the switchback operation has completed: metrocluster show
    Example
    The switchback operation is still running when a cluster is in the waiting-for-switchback state:
    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 normal state.:

    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 show command.
  11. Reestablish any SnapMirror or SnapVault configurations.