PowerScale OneFS 9.3.0.0 CLI Administration Guide

Recover SmartLock compliance directories on a target cluster

You can recover compliance SmartLock directories that you have replicated to a secondary cluster running OneFS 7.2.1 or earlier versions.

1. On the secondary cluster, enable writes to the SmartLock directories that you want to recover.
   • If the last replication job completed successfully and a replication job is not currently running, run the isi sync recovery allow-write command on the secondary cluster.

     For example, the following command enables writes to the target directory of SmartLockSync:

     isi sync recovery allow-write SmartLockSync

   • If a replication job is currently running, wait until the replication job completes, and then run the isi sync recovery allow-write command.
   • If the primary cluster became unavailable while a replication job was running, run the isi sync target break command. Note that you should only break the association if the primary cluster has been taken offline permanently.

     For example, the following command breaks the association for the target directory of SmartLockSync:

     isi sync target break SmartLockSync

2. If you ran isi sync target break, restore any files that are left in an inconsistent state.
   1. Delete all files that are not committed to a WORM state from the target directory.
   2. Copy all files from the failover snapshot to the target directory.
      Failover snapshots are named according to the following naming pattern:

      SIQ-Failover-<policy-name>-<year>-<month>-<day>_<hour>-<minute>-<second>
      

      Snapshots are located under the hidden directory /ifs/.snapshot.

3. If any SmartLock directory configuration settings, such as an autocommit time period, were specified for the source directory of the replication policy, apply those settings to the target directory.
   Because autocommit information is not transferred to the target cluster, files that were scheduled to be committed to a WORM state on the source cluster would not be scheduled to be committed at the same time on the target cluster. To ensure that all files are retained for the appropriate time period, you can commit all 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 --domain /ifs/data/smartlock
   --autocommit-offset 1m