When the failover is complete, and the source cluster is operational, the failback process may commence with the following steps:
Source-cluster# isi sync recovery resync-prep [Policy Name]
To check the current status of the resync-prep, with duration, transfer, and throughput, run the following command:
Source-cluster# isi sync jobs reports list
This action causes SyncIQ to create a mirror policy for the replication policy on the target cluster. The mirror policy is placed under Data Protection > SyncIQ > Local Targets on the target cluster.
SyncIQ names mirror policies according to the following pattern:
To stop services on the target cluster, run the following commands:
Target-cluster# isi services smb disable
Target-cluster# isi services nfs disable
Target-cluster# isi services vsftpd disable
Target-cluster# isi sync jobs start -–policy-name=[Mirror Policy Name]
If required, the mirror policy on the target cluster may be modified to specify a schedule for the policy to run.
Note: Prior to proceeding to the next step, ensure that the mirror policy completes successfully, otherwise data may be lost and unrecoverable.
Source-cluster# isi sync recovery allow-write –-policy-name=[Policy Name]
Target-cluster# isi sync recovery resync-prep [Policy Name]
This places the target cluster back into read-only mode and ensures that the data sets are consistent on both the source and target clusters.
Redirect clients to begin accessing their data on the source cluster. Although not required, it is safe to remove a mirror policy after failback has completed successfully.