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 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
Introduction to SmartLock compatibilty
Compliance mode
Failover and failback with SmartLock
SmartLock and SyncIQ security
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 to SmartLock compatibilty

Home > Storage > PowerScale (Isilon) > Product Documentation > Data Protection > Dell PowerScale SyncIQ: Architecture, Configuration, and Considerations > Introduction to SmartLock compatibilty

Introduction to SmartLock compatibilty

  • Data replication is a crucial requirement for many WORM protected data sets. OneFS provides WORM functionality through SmartLock, which is compatible with SyncIQ for data replication.

    For SyncIQ and SmartLock environments, you must ensure that all node clocks are synchronized. Therefore, having all nodes on the source and target clusters configured with Network Time Protocol (NTP) Peer Mode is recommended. If Compliance SmartLock is required, all source and target nodes must be configured in NTP Peer Mode before the compliance clock is configured.

    Replicating data from a source SmartLock directory to a target SmartLock directory, ensures that all metadata related to the retention date and commit status persists on the target. On the contrary, replicating from a SmartLock directory to a non-SmartLock directory causes all metadata relating to the retention date and commit status to be lost.

    It is recommended to have to the source and target directory in the same compliance mode. In many environments, it may not be possible to have the source and target directories in the same compliance mode. Depending on the source and target directory types, SyncIQ may be compatible. However, to confirm if the source and target directories are compatible with SmartLock, see the following table.

    Table 3.   SyncIQ SmartLock source to target compatibility

    Source directory type

    Target directory type

    SyncIQ source-to-target compatibility

    Failback allowed

    Non-SmartLock

    Non-SmartLock

    Yes

    Yes

    Non-SmartLock

    Enterprise SmartLock

    Yes

    Yes, unless files are committed to a WORM state on the target cluster.

    Non-SmartLock

    Compliance SmartLock

    No

    No

    Enterprise SmartLock

    Non-SmartLock

    Yes, replication type is allowed. However, retention will not be enforced.

    Yes, however, files will not have WORM status.

    Enterprise SmartLock

    Enterprise SmartLock

    Yes

    Yes, any newly committed WORM files will be included.

    Enterprise SmartLock

    Compliance SmartLock

    No

    No

    Compliance SmartLock

    Non-WORM

    No

    No

    Compliance SmartLock

    Enterprise SmartLock

    No

    No

    Compliance SmartLock

    Compliance SmartLock

    Yes

    Yes, any newly committed WORM files will be included.