Fail over data to a secondary cluster

You can fail over to a secondary Isilon cluster if your primary cluster becomes unavailable.

Before you begin

You must have created and successfully run a replication policy on the primary cluster. This action replicates data to the secondary cluster.

About this task

Note Image

Data failover is supported both for SmartLock enterprise and compliance directories. A SmartLock compliance directory requires its own separate replication policy.

Complete the following procedure for each replication policy that you want to fail over.

Procedure

  1. If your primary cluster is still online, complete the following steps:
    1. Stop all writes to the replication policy's path, including both local and client activity.
      This action ensures that new data is not written to the policy path as you prepare for failover to the secondary cluster.
    2. Modify the replication policy so that it is set to run only manually.
      This action prevents the policy on the primary cluster from automatically running a replication job. If the policy on the primary cluster runs a replication job while writes are allowed to the target directory, the job fails and the replication policy is deactivated. If this happens, modify the policy so that it is set to run only manually, resolve the policy, and complete the failback process. After you complete the failback process, you can modify the policy to run according to a schedule again.
  2. On the secondary cluster, click Data Protection > SyncIQ > Local Targets.
  3. In the SyncIQ Local Targets table, select More > Allow Writes for a replication policy.
  4. Re-enable client access, and direct users to begin accessing their data from the secondary cluster.