Overview of the unplanned failback process
After an unplanned failover, when the source cluster comes up, you can use the following unplanned failback process to return control to the original source cluster:
Make sure that you are logged into the source cluster.
Note:
Before starting the failback process, verify that the episodic replication service is running on the primary node. If the service is not running on the primary node, stop the service using the Replication> episodic service stop command and start it again using the Replication> episodic service start command.
Use the Replication> episodic job failover force=yes/no job_name current_cluster_link command to configure the current source cluster as a valid target to the new source cluster. This command should be executed from the old source cluster.
Use the Replication> episodic job sync job_name command from the new source cluster to synchronize file system data with the newly added destination cluster.
Use the Replication> episodic job failback force=yes/no job_name current_cluster_link command to move control of the episodic replication job from the destination cluster back to the source cluster.
Use the Replication> episodic job sync job_name command to ensure that the episodic replication job is in a well-defined state and incremental episodic replication can be resumed.
Note:
An administrator can use the Replication> episodic job destroy force command to clean up local job configuration. Configuration of the other clusters, which are part of the job, will not be modified and any episodic replication units will be disassociated from job. The Replication> episodic job destroy force and Replication> episodic repunit destroy force commands should be used in the event of an unrecoverable configuration or episodic replication direction mismatch.