The
SnapMirror relationship in
SnapLock has certain limitations.
- The
SnapMirror relationship is not allowed if the source is a non-WORM volume and the destination is a
SnapLock Compliance volume.
- The
SnapMirror relationship is not allowed if the source is a
SnapLock Enterprise volume and the destination is a
SnapLock Compliance volume.
- A volume
SnapMirror relationship is not allowed between two
SnapLock Compliance volumes if the destination volume has unexpired files.
- Deletion of a
Snapshot copy on a
SnapLock Compliance volume is not allowed if the volume is part of a
SnapMirror relationship and the
Snapshot copy is locked by
SnapMirror. This protects you from accidentally deleting the base
Snapshot copy of a volume
SnapMirror relationship on a
SnapLock Compliance volume.
- On a
SnapLock Compliance volume, if a volume
SnapMirror relationship is broken, it can never be reestablished.
- In a SnapMirror or vol copy operation from a regular volume to a SnapLock volume, all SnapLock related volume options are cleared out and the no_atime_update volume option is set to on in the SnapLock volume.