Fail back data to a primary cluster

After you fail over to a secondary cluster, you can fail back to the primary cluster.

Before you begin

Before you can fail back to the primary cluster, you must already have failed over to the secondary cluster. Also, you must ensure that your primary cluster is back online.

About this task

Note Image

Data failback is supported for SmartLock compliance and enterprise directories. If clients committed new SmartLock files while the secondary cluster was in operation, these SmartLock files are replicated to the primary cluster during failback.

Procedure

  1. On the primary cluster, click Data Protection > SyncIQ > Policies.
  2. In the SyncIQ Policies list, for a replication policy, click More > Resync-prep.

    This action causes SyncIQ to create a mirror policy for the replication policy on the secondary cluster. The mirror policy is placed under Data Protection > SyncIQ > Local Targets on the secondary cluster.

    SyncIQ names mirror policies according to the following pattern:
    <replication-policy-name>_mirror
  3. Before beginning the failback process, prevent clients from accessing the secondary cluster.
    This action ensures that SyncIQ fails back the latest data set, including all changes that users made to data on the secondary cluster while the primary cluster was out of service. We recommend that you wait until client activity is low before preventing access to the secondary cluster.
  4. On the secondary cluster, click Data Protection > SyncIQ > Policies.
  5. In the SyncIQ Policies list, for the mirror policy, click More > Start Job.
    Alternatively, you can edit the mirror policy on the secondary cluster, and specify a schedule for the policy to run.
  6. On the primary cluster, click Data Protection > SyncIQ > Local Targets.
  7. On the primary cluster, in the SyncIQ Local Targets list, for the mirror policy, select More > Allow Writes.
  8. On the secondary cluster, click Data Protection > SyncIQ > Policies.
  9. On the secondary cluster, in the SyncIQ Policies list, click More > Resync-prep for the mirror policy.
    This puts the secondary cluster back into read-only mode and ensures that the data sets are consistent on both the primary and secondary clusters.

What to do next

Redirect clients to begin accessing their data on the primary cluster. Although not required, it is safe to remove a mirror policy after failback has completed successfully.