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

Assumptions

Assumptions

    • In order to failover to an associated cluster, a SyncIQ policy must exist between the source and target cluster, as explained in Configuring a SyncIQ policy.
    • If the policy is configured, it must have successfully run at least once.
    • All system configuration is complete on the target cluster, emulating the source cluster’s configuration. This includes licensing, access zones, SmartConnect, shares, authentication providers, etc.
    • This section does not consider any network or other environmental changes required. During disaster readiness testing, ensure that all other environmental steps are documented and shared with administrators.

    Note: As a best practice, configure DNS to require a single forwarding change only. During an outage, this minimizes downtime and simplifies the failover process.