How privileged delete affects mirroring interactions

Using SnapMirror, you can replicate a SnapLock Enterprise volume to a non-WORM or another SnapLock Enterprise volume.

If privileged delete is enabled on a SnapLock Enterprise source volume, and the destination is also a SnapLock Enterprise volume, the transfer of the privileged delete state depends on the type of mirroring used. However, to use the privileged delete functionality at the destination, you need to break the SnapMirror relationship and make the destination volume writable.

In the case of a volume SnapMirror relationship, the privileged delete state of the source volume is transparently transferred to the volume SnapMirror destination volume irrespective of the type of the source and destination volumes. For a SnapLock Enterprise volume and a regular volume, the initial state is uninitialized; for a SnapLock Compliance volume the initial state is disallowed. In this type of mirroring, the state of privileged delete feature on the final destination is the same as the source volume.

In the case of a qtree SnapMirror relationship, the privileged delete state of the source is not transferred to the destination.

Note: You must separately replicate the log volume to the SnapMirror destination for maintaining complete information about all the privileged delete activity associated with the replicated SnapLock Enterprise volume.