You can fail over to a secondary
PowerScale cluster if your primary cluster becomes unavailable.
You must have created and successfully run a replication policy on the primary cluster. This action replicates data to the secondary cluster.
NOTE: 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.
If your primary cluster is still online, complete the following steps:
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.
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.
On the secondary cluster, click
Data Protection > SyncIQ > Local Targets.
In the
SyncIQ Local Targets table, select
More > Allow Writes for a replication policy.
Re-enable client access, and direct users to begin accessing their data from the secondary cluster.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\