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
Introduction
Failover
Target cluster dataset
Failback
Allow-writes compared to break association
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 Appendix B: SyncIQ encryption with self-signed certificates Appendix C: Configuring cascaded replication Appendix D: Configuring custom replication Appendix E: Technical support and resources

Introduction

Introduction

  • Under normal operation, SyncIQ target directories can be written to only by the SyncIQ job itself – all client writes to any target directory are disabled, this is referred to as a protected replication domain. In a protected replication domain, files cannot be modified, created, deleted, or moved within the target path of a SyncIQ job.

    Figure 28.    PowerScale SyncIQ failover and failback

    SyncIQ provides built-in recovery to the target cluster with minimal interruption to clients. By default, the RPO (recovery point objective) is to the last completed SyncIQ replication point. Optionally, with the use of SnapshotIQ, multiple recovery points can be made available, as explained in SnapshotIQ and SyncIQ.

    Note: SyncIQ Failover and Failback does not replicate cluster configurations such as SMB shares and NFS exports, quotas, snapshots, and networking settings, from the source cluster. PowerScale does copy over UID/GID ID mapping during replication. In the case of failover to the remote cluster, other cluster configurations must be configured manually. An application such as Superna Eyeglass can be used to