Management of WORM Snapshot copies by using SnapVault

How Snapshot copies retention works on SnapLock volumes
SnapVault uses the count field of the SnapVault schedule on the secondary storage system to determine the number of Snapshot copies that are retained.
How Snapshot copies are named on SnapLock volumes
Snapshot copies created by SnapVault on SnapLock volumes use a different naming scheme from that used by Snapshot copies for regular volumes.
Retention period for WORM Snapshot copies created by SnapVault
You can configure the schedules on the SnapVault secondary storage system to create WORM Snapshot copies and specify a retention period.
Listing Snapshot copies on the WORM volume
WORM Snapshot copies are identified by the word snaplock at the end of each Snapshot copy entry.
Listing Snapshot copies and retention dates
You can list Snapshot copies and retention dates.
Deleting expired WORM Snapshot copies
You can delete WORM Snapshot copies that are retained beyond their retention periods.
How to retain more than 255 SnapVault Snapshot copies
The limit imposed by Data ONTAP for retaining Snapshot copies is 255. However, if you need to retain more than 255 Snapshot copies, you can do so by creating a new volume.
Backup of the log volumes created by the SnapLock for SnapVault feature
Along with backing up SnapLock Compliance secondary storage volumes, you can provide additional protection for log volumes created by the SnapLock for SnapVault feature.
How to resynchronize a broken SnapVault relationship
You can use the snapvault start -r command to reestablish a broken SnapVault relationship without a lengthy baseline transfer.
Turning SnapVault off
You might want to turn SnapVault off because the files are no longer important or current or have been moved to another location.

Parent topic: Guidelines for using the SnapLock for SnapVault feature