Overview of the unplanned failback process

After an unplanned failover, when the original source cluster (cluster A) comes up, you can use the following unplanned failback process to retain the replication between source and destination cluster.

When the original source cluster (cluster A) comes up, it still acts as the primary cluster. At this time, both the source and the destination clusters show the same status.

For unplanned failback, run the following command from the original source cluster (cluster A):

Replication> continuous failback fs_name

Where fs_name is the name of the file system which is configured under continuous replication.

Once, an unplanned failback happens, the original source cluster (cluster A) becomes the new destination cluster. The file system is still online at new source cluster (cluster B).