Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Dell PowerScale SyncIQ: Architecture, Configuration, and Considerations
Executive summary Introduction Deployment topologies Use cases Architecture and processes Data replication Configuring a SyncIQ policy Impacts of modifying SyncIQ policies SyncIQ performance rules SnapshotIQ and SyncIQ SyncIQ design considerations Failover and failback Superna Eyeglass DR Edition SyncIQ and CloudPools SyncIQ security SyncIQ bandwidth reservations Monitoring, alerting, reporting, and optimizing performance Administration SyncIQ replication and data reduction 16 TiB large file support and SyncIQ implications OneFS version compatibility SmartLock compatibility Conclusion Appendix A: Failover and failback steps
Introduction
Assumptions
Failover
Failback
Appendix B: SyncIQ encryption with self-signed certificates Appendix C: Configuring cascaded replication Appendix D: Configuring custom replication Appendix E: Technical support and resources

Failback

Failback

  • When the failover is complete, and the source cluster is operational, the failback process may commence with the following steps:

    1. On the source cluster, click Data Protection > SyncIQ > Policies. In the SyncIQ Policies list, for the associated replication policy, click More > Resync-prep. Alternatively, from the source cluster CLI, run the following command:

    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:

    <replication-policy-name>_mirror

    1. Before beginning the failback process, prevent clients from accessing the target cluster. In large environments it may be difficult to stop all clients from writing data, it may be easier to stop SMB, NFS, and FTP services on the source cluster.

    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

    1. On the target cluster, click Data Protection > SyncIQ > Policies. In the SyncIQ Policies list, for the mirror policy, click More > Start Job. Alternatively, to start the mirror policy from the CLI, run the following command:

    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.

    1. On the source cluster, click Data Protection > SyncIQ > Local Targets. In the SyncIQ Local Targets list, for the mirror policy, select More > Allow Writes. Alternatively, to perform the allow writes from the CLI, run the following command:

    Source-cluster# isi sync recovery allow-write –-policy-name=[Policy Name]

    1. On the target cluster, click Data Protection > SyncIQ > Policies. For the appropriate mirror policy in the SyncIQ Policies list, click More > Resync-prep. Alternatively, to perform the resync-prep from the CLI, run the following command:

    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.

    Finalizing the failback

    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.