Failover to the secondary site

When the primary site stops functioning, all applications must move to the secondary site to ensure continuity. Run the following command on the secondary to convert the secondary site into acting primary site: mmafmctl <FileSystemName> failoverToSecondary -j <FilesetName> [--norestore |--restore ].

You can use the --restore option to restore the data from latest snapshot or the --norestore option to keep the all existing data during the failover process on the secondary site. The --norestore option is the default option. After the failover, the secondary site acts as a primary site and hosts 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.