Failover to the secondary site

When the primary site stops functioning, all applications must be moved to the secondary site to ensure stability. Run mmafmctlDevice failoverToSecondary -j FilesetName [--norestore |--restore ] to convert the secondary site to the active primary site.

You can restore the latest snapshot data on the secondary site during the failover process, or keep the existing data. The --norestore option is the default value, which keeps the existing data. After failover, the secondary site becomes acting primary and is ready to host applications.

The customer must ensure that the NFS export used for the secondary site is not removed so that after failback to the primary, the original primary site can communicate with the secondary site, which is the current primary . Also, the RPO snapshots existing on the current primary must not be deleted because the RPO snapshots are used during the failback process when the original primary site starts functioning again.

RPO snapshots are temporarily disabled on the active primary site. The new data is not replicated to any other site until a new primary is set up, or the original primary is reinstalled, and the current primary is converted back to the secondary site.