Creating a SnapLock volume

You must create a SnapLock volume for the files or Snapshot copies that you want to commit to the WORM state. The volume inherits the SnapLock mode—Compliance or Enterprise—from the SnapLock aggregate, and the ComplianceClock time from the node.

Before you begin

The SnapLock aggregate must be online.

About this task

You can destroy or rename an Enterprise volume at any time. You cannot destroy a Compliance volume until the retention period has elapsed. You can never rename a Compliance volume.

You can clone SnapLock volumes, but you cannot clone files on a SnapLock volume.

Note: LUNs are not supported on SnapLock volumes. Although it is possible to move LUNs onto a SnapLock volume using legacy technology, this is not a supported operation, nor is any other operation involving LUNs on a SnapLock volume.

Procedure

Create a SnapLock volume: volume create -vserver SVM_name -volume volume_name -aggregate aggregate_name
For a complete list of options, see the man page for the command. The following options are not available for SnapLock volumes: -nvfail, -atime-update, -is-autobalance-eligible, -space-mgmt-try-first, and vmalign.

The following command creates a SnapLock Compliance volume named vol1 on aggr1 on vs1:

cluster1::> volume create -vserver vs1 -volume vol1 -aggregate aggr1