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 to SyncIQ Deployment topologies Use cases Architecture and processes Data replication Configuring a SyncIQ policy Impacts of modifying SyncIQ policies
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 Appendix B: SyncIQ encryption with self-signed certificates Appendix C: Configuring cascaded replication Appendix D: Configuring custom replication Appendix E: Technical support and resources

Impacts of modifying SyncIQ policies

Home > Storage > PowerScale (Isilon) > Product Documentation > Data Protection > Dell PowerScale SyncIQ: Architecture, Configuration, and Considerations > Impacts of modifying SyncIQ policies

Impacts of modifying SyncIQ policies

  • SyncIQ policies may be modified and updated through the CLI or the web interface. The impact of the change is dependent upon how the policy is modified. Rather than modifying or deleting a policy when a suspension is required, the policy may also be disabled, allowing for it to be reenabled with minimal impact at a later point.

    After a policy is configured and the policy has run, SyncIQ will run either the initial replication again or a differential replication if the following variables are modified:

    • Source directory
    • Included or excluded directories
    • File criteria: type, time, and regular expressions
    • Target cluster, even if the new target cluster is identical to the old target cluster

    IP and DNS changes will not trigger a full replication. However, if the cluster GUID changes, the job will fail at runtime. Also, unlike the other settings, a manual reset of the affected policy is required in order to be able to run an associated job.

    • Target directory

    If a SyncIQ replication policy is deleted, replication jobs will not be created for the policy. Any snapshots and reports associated with the policy are also deleted. The target cluster will break the association to the source cluster, removing the local target entry, and the target directory will allow writes.