Failing back to the new primary site

You can configure a new primary if the old primary site stopped functioning.

Important: For a planned or unplanned failure, it is recommended to use the role reversal method instead of failover and failback methods. For more information about the role reversal, see Role reversal.

Complete the following steps to configure a new primary site:

Create a GPFS fileset on the new primary site. This fileset is configured as the new primary.
Create the latest snapshot from the acting primary by running the mmafmctl command with the replacePrimary option.
A new psnap0 with all the latest contents is created on the current primary server. This snapshot is used in the subsequent steps in this task.
Copy the contents from the snapshot to the new primary site by using scp or other means outside of AFM.
The snapshot that is created from the acting primary is an argument to the --secondary-snapname option. Issue the following command to convert the fileset on the primary site:
```
# mmafmctl Device convertToPrimary -j FilesetName
[--afmtarget Target { --inband | --secondary-snapname SnapshotName}] 
[ --check-metadata | --nocheck-metadata ][--rpo RPO] [-s LocalWorkDirectory]
```
The primary ID is generated and a psnap0 with the same name is created on the primary site. After the ID generation and the snapshot creation, complete all the steps in Failing back to the old primary site.