Skip to main content

Performing a forced switchover

The switchover process, in addition to providing nondisruptive operations during testing and maintenance, enables you to recover from a site failure with a single command.

Before you begin

  • At least one of the surviving site nodes must up and running before you perform the switchover.

  • All previous configuration changes must be complete before performing a switchback operation.

    This is to avoid competition with the negotiated switchover or switchback operation.

Note
SnapMirror and SnapVault configurations are deleted automatically.

About this task

The metrocluster switchover command switches over the nodes in all DR groups in the MetroCluster configuration. For example, in an eight-node MetroCluster configuration, it switches over the nodes in both DR groups.

  1. Implement the switchover by running the metrocluster switchover -forced-on-disaster true command.

    The operation can take a period of minutes to complete.

  2. Answer y when prompted to continue with the switchover.
  3. Verify that the switchover was completed successfully by running the metrocluster operation show command.

    Example

    mcc1A::> metrocluster operation show
      Operation: switchover
     Start time: 10/4/2012 19:04:13
          State: in-progress
       End time: -
         Errors: 

    mcc1A::> metrocluster operation show
      Operation: switchover
     Start time: 10/4/2012 19:04:13
          State: successful
       End time: 10/4/2012 19:04:22
         Errors: -


    If the switchover is vetoed, you have the option of reissuing the metrocluster switchover -forced-on-disaster true command with the –override-vetoes option. If you use this optional parameter, the system overrides any soft vetoes that prevented the switchover.

After you finish

SnapMirror relationships need to be reestablished after switchover.