Following are some questions about SnapLock volumes.
You cannot convert a SnapLock Enterprise volume to a SnapLock Compliance volume. However, you can copy a SnapLock volume to another volume by using the vol copy command. You can copy between the SnapLock volumes or regular volumes. If the source volume is a SnapLock Enterprise volume and the destination volume is a SnapLock Compliance volume, then the destination volume must be an equivalently sized or larger Compliance volume. However, if the destination volume is a SnapLock Compliance volume, you must ensure that the volume is empty, that is, it does not contain any unexpired files. The volumes, other than of the type SnapLock volume (Enterprise or Compliance), should have the same attributes of minimum, maximum, and default retention periods specified. The vol copy command retains the retention period attribute of the files and also preserves the WORM attribute of the files in the SnapLock Enterprise volume.
Use the vol copy command to copy between SnapLock volumes or regular volumes. Following table shows you all the possible combinations that are allowed for performing the vol copy command:
No. You cannot convert an existing non-SnapLock volume to a SnapLock volume or vice versa primarily because this opens up many potential security holes regarding the disposition of existing content of the volume and would jeopardize compliance as well as complicate the user interfaces. The only way to place existing data on a SnapLock volume is to copy the files to a SnapLock volume and transition each individual file from read-write state to read-only state. The setting of the retention period is optional, because a file uses the volume's default retention period if no retention period is specified. Replicating a non-SnapLock volume to a SnapLock volume does not engage the SnapLock locking mechanism. Only the transition from read-write state to read-only state locks the file.
sys1>aggr status
Aggr State Status Options
wormaggr_sle online raid_dp,aggr snaplock_enterprise
wormvol_trad_slc online raid4,trad snaplock_compliance
wormvol_trad_sle online raid4,trad snaplock_enterprise
wormaggr_slc online raid_dp,aggr snaplock_compliance
aggr0 online raid4,aggr root
There are no restrictions on creation, deletion, or number of Snapshot copies on SnapLock volumes beyond the normal system limits because there is no risk of data loss with these operations. This means that SnapMirror, dump, and all other Snapshot copy-based technologies will not be fundamentally impaired when dealing with SnapLock volumes. You can also use the snap restore command to restore a previous Snapshot copy on SnapLock Enterprise volumes even though doing so might involve data loss because the operating model of SnapLock Enterprise is that the storage administrator is trusted. However, you cannot use the snap restore command to restore a previous Snapshot copy on SnapLock Compliance volumes. The whole premise of restoring to a previous Snapshot copy is that you are throwing away all modifications that occurred subsequent to the point in time at which the Snapshot copy was taken in order to revert to a previous consistent state of the file system. This is diametrically opposed to the permanence guarantees provided by the untrusted administrator model of SnapLock Compliance and cannot be allowed. To allow such an operation would violate regulatory compliance requirements.
It depends on the type of SnapLock volume and the Data ONTAP release. Regulatory compliance requires preventing the destruction of any records that have not aged past their assigned retention period. This requirement puts heavy constraints on the allowable destructive administrative operations that can be performed on SnapLock Compliance volumes. The trusted administrator model of SnapLock Enterprise makes life much easier for SnapLock Enterprise volumes.
SnapLock is the fundamental property of an aggregate and not a volume. All volumes created on a SnapLock aggregate automatically and permanently inherit the SnapLock type of the aggregate. This means that you cannot have SnapLock volumes on non-SnapLock aggregates and vice versa. You also cannot have SnapLock Enterprise and Compliance volumes on the same aggregate. The virtual volume type is inherited from the SnapLock aggregate type.
Yes, as long as you do not attempt to shrink SnapLock FlexVol volumes below the actual used capacity.