PowerScale OneFS 9.8.0.0 Web Administration Guide

PDF

SmartLock replication limitations

Be aware of the limitations of replicating and failing back SmartLock directories with SyncIQ.

If the source directory or target directory of a SyncIQ policy is a SmartLock directory, replication and failback might not be allowed. For more information, see the following table:

Table 1. Source and Target Directory TypesThe following table displays the permissions for each directory type.
Source directory type	Target directory type	Replication Allowed	Failback allowed
Non-SmartLock	Non-SmartLock	Yes	Yes
Non-SmartLock	SmartLock enterprise	Yes	Yes, unless files are committed to a WORM state on the target cluster
Non-SmartLock	SmartLock compliance	No	No
SmartLock enterprise	Non-SmartLock	Yes; however, retention dates and commit status of files are lost.	Yes; however, the files do not have WORM status
SmartLock enterprise	SmartLock enterprise	Yes	Yes; any newly committed WORM files are included
SmartLock enterprise	SmartLock compliance	No	No
SmartLock compliance	Non-SmartLock	No	No
SmartLock compliance	SmartLock enterprise	No	No
SmartLock compliance	SmartLock compliance	Yes	Yes; any newly committed WORM files are included

If you are replicating a SmartLock directory to another SmartLock directory, you must create the target SmartLock directory before running the replication policy. Although OneFS creates a target directory automatically if a target directory does not exist, OneFS does not create a target SmartLock directory automatically. If you attempt to replicate an enterprise directory before the target directory has been created, OneFS creates a non-SmartLock target directory and the replication job succeeds. If you replicate a compliance directory before the target directory has been created, the replication job fails.

If you replicate SmartLock directories to another PowerScale cluster with SyncIQ, the WORM state of files is replicated. However, SmartLock directory configuration settings are not transferred to the target directory.

For example, if you replicate a directory that contains a committed file that is set to expire on March 4, the file is still set to expire on March 4 on the target cluster. However, if the directory on the source cluster is set to prevent files from being committed for more than a year, the target directory is not automatically set to the same restriction.

In the scenario where a WORM exclusion domain has been created on an enterprise mode or compliance mode directory, replication of the SmartLock exclusion on the directory occurs only if the SyncIQ policy is rooted at the SmartLock domain that contains the exclusion. If this condition is not met, only data is replicated, and the SmartLock exclusion is not created on the target directory.