Table of ContentsView in Frames

What happens during failover

When you start the failover process, the NetApp Management Console data protection capability breaks the SnapMirror relationship between the source storage containers in the primary data node and their destination storage containers in the disaster recovery node and activates the disaster recovery node containers as the active systems that can be accessed by users.

When you invoke failover, the NetApp Management Console provisioning capability puts the dataset into "failing over" state and carries out the following processes.

  1. Runs a failover script (if one is specified by the protection policy) to stop applications writing data to the primary storage systems.
  2. Quiesces all SnapMirror related activity between the primary storage systems and their partners in the disaster recovery node.
  3. Breaks all SnapMirror relationships between the primary storage systems and their partners in the disaster recovery node.
  4. Puts any mirrored LUNs in the online state.
  5. Runs a failover script (if one is specified by the protection policy) to restart applications writing data to the secondary systems in the disaster recovery node.
  6. Enables the same export protocols (CIFS, NFS, iSCSI, or FC) for the containers in the disaster recovery node as were enabled for the containers in the primary storage systems.
  7. After the above processes are complete, changes the dataset out of failing over state.

If the above processes complete successfully, the dataset state is changed to "failed over." You can now direct or re-map users to access their data from storage in the disaster recovery node.

If one of the above processes failed, the state is changed to "failover error."