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

Failover

Failover

  • After a policy is configured and run successfully, a failover may be initiated with the following steps:

    1. If the source cluster is online, stop all writes impacting the directory path of the replication policy, limiting any new data from being written on the 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 source cluster, run the following commands:  

    Source-cluster# isi services smb disable

    Source-cluster# isi services nfs disable

    Source-cluster# isi services vsftpd disable

    1. If the source cluster is online, ensure that any scheduled policies on the source cluster do not replicate data during the failover. Place the policies in manual mode by running the following command:

    Source-cluster# isi sync policies modify [Policy Name] –schedule “”

    1. If the source cluster is online, run the associated policy manually by running the following command:

    Source-cluster# isi sync jobs start [Policy Name]

    Ensure that the policy completes prior to proceeding to the next step.

    1. On the target cluster, from the web interface click Data Protection > SyncIQ > Local Targets. From the “Local Targets” tab, scroll to the appropriate policy and select More > Allow Writes. To perform this from the CLI, run the following command:

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

    At this point, the target cluster is now accessible and writable.

    Clients must now be re-directed to the target cluster to continue accessing the file system. Make any necessary network, DNS, and environmental updates. Depending on the DNS configuration, a single DNS update only changing the forwarding is sufficient.