Creating SnapLock destination volumes

What SnapLock volumes are

SnapLock volumes are Write-Once-Read-Many (WORM) volumes that you create for data you want to archive permanently. There are two types of SnapLock volumes:

SnapLock Compliance volume--for strict regulatory environments, such as SEC 17a-4 compliant environments
SnapLock Enterprise volume--for environments without regulatory restrictions.

For details about licensing and creating SnapLock volumes, see the System Administration Storage Management Guide.

SnapLock destination volume restrictions

A SnapMirror destination volume created as a SnapLock Compliance volume has the following restrictions:

You cannot use the snapmirror resync command to return a former destination volume and resynchronize its content with the source.
You cannot reinitialize a SnapLock Compliance destination volume because data on the volume cannot be changed. If you break the SnapMirror relationship between the source and destination volumes using the snapmirror break command, Data ONTAP prevents you from ever reestablishing the SnapMirror relationship with the same SnapLock Compliance destination volume.
You can initalize a new empty SnapLock Compliance destination volume.

A SnapMirror destination volume created as a SnapLock Enterprise volume is the same as a destination volume created for a non-SnapLock volume. You can perform all the same administrative tasks on a SnapLock Enterprise destination that you can perform on a non-SnapLock destination.

Creating a SnapLock Compliance SnapMirror relationship

To create a SnapMirror relationship from a SnapLock Compliance volume to a SnapLock Compliance destination volume, complete the following steps.

Note
This procedure assumes you have read about basic SnapMirror setup and you have experience with creating SnapMirror relationships. See Setting up a basic SnapMirror operation for a details about first-time SnapMirror setup.

Step	Action
1	On the administration host, create or edit the snapmirror.conf file on the destination filer to specify the SnapLock Compliance volume source and destination. Example The following entry specifies asynchronous mirroring from vol1 of s_filer and vol2 of d_filer using the default replication arguments. s_filer:vol1 d_filer:vol2 - * * * *
2	On the destination filer console, create the destination volume using the `vol create` command. Example vol create vol2 2 Caution Do not use the `vol create -L` command to create a SnapLock Compliance volume because volume SnapMirror cannot use it as a destination volume.
3	On the destination filer console, mark the volume as restricted using the `vol restrict` command.
4	On the destination filer console, create an initial complete (baseline) copy of the source on the destination and start the mirroring process using the `snapmirror initialize -L` command. Result After successfully completing the baseline transfer, Data ONTAP converts the destination volume to a SnapLock Compliance destination volume before bringing it online. Example snapmirror initialize -S s_filer:vol1 -L d_filer:vol2 Note After the destination volume is converted to a SnapLock Compliance destination volume, it will always be a SnapLock Compliance volume and cannot be changed.

Creating a SnapLock Enterprise SnapMirror relationship

Creating a SnapMirror relationship from a SnapLock Enterprise source volume to a SnapLock Enterprise destination volume is the same as creating a SnapMirror relationship for non-SnapLock Enterprise volumes. See Setting up a basic SnapMirror operation for a details about first-time SnapMirror creation.

Creating SnapLock destination volumes

What SnapLock volumes are

SnapLock destination volume restrictions

Creating a SnapLock Compliance SnapMirror relationship

Example

Example

Result

Example

Creating a SnapLock Enterprise SnapMirror relationship