Migrate SmartLock compliance directories

You can migrate SmartLock compliance directories from a recovery cluster, either by replicating the directories back to the original source cluster, or to a new cluster. Migration is necessary only when the recovery cluster is running OneFS 7.2.1 or earlier. These OneFS versions do not support failover and failback of SmartLock compliance directories.

Procedure

  1. On the recovery cluster, create a replication policy for each SmartLock compliance directory that you want to migrate to another cluster (the original primary cluster or a new cluster).

    The policies must meet the following requirements:

    • The source directory on the recovery cluster is the SmartLock compliance directory that you are migrating.
    • The target directory is an empty SmartLock compliance directory on the cluster to which the data is to be migrated. The source and target directories must both be SmartLock compliance directories.
  2. Replicate recovery data to the target directory by running the policies that you created.

    You can replicate data either by manually starting the policies or by specifying a schedule.

  3. Optional: To ensure that SmartLock protection is enforced for all files, commit all migrated files in the SmartLock target directory to a WORM state.
    Because autocommit information is not transferred from the recovery cluster, commit all migrated files in target SmartLock directories to a WORM state.
    For example, the following command automatically commits all files in /ifs/data/smartlock to a WORM state after one minute:
    isi worm domains modify /ifs/data/smartlock --autocommit-offset 1m
    This step is unnecessary if you have configured an autocommit time period for the SmartLock directories being migrated.
  4. On the cluster with the migrated data, click Data Protection > SyncIQ > Local Targets.
  5. In the SyncIQ Local Targets table, for each replication policy, select More > Allow Writes.
  6. Optional: If any SmartLock directory configuration settings, such as an autocommit time period, were specified for the source directories of the replication policies, apply those settings to the target directories on the cluster now containing the migrated data.
  7. Optional: Delete the copy of the SmartLock data on the recovery cluster.
    You cannot recover the space consumed by the source SmartLock directories until all files are released from a WORM state. If you want to free the space before files are released from a WORM state, contact Isilon Technical Support for information about reformatting your recovery cluster.