Archive and Compliance Power Guide
This document is available in PDF format:
- Deciding whether to use the Archive and Compliance Power Guide
This guide describes how to use Lenovo SnapLock technology to retain files in unmodified form for regulatory and governance purposes. It shows you how to commit files and Snapshot copies towrite once, read many
(WORM) storage, and how to set retention periods for WORM-protected data. - What SnapLock is
SnapLock is a high-performance compliance solution for organizations that use WORM storage to retain files in unmodified form for regulatory and governance purposes. A single license entitles you to use SnapLock in strict Compliance mode, to satisfy external mandates like SEC Rule 17a-4, and a looser Enterprise mode, to meet internally mandated regulations for the protection of digital assets. - SnapLock workflow
You specify which SnapLock mode you want to use, Compliance or Enterprise, when you create a SnapLock aggregate. The SnapLock volume you create inherits the setting. You typically use a file archiving application to move files from primary storage to the SnapLock volume. - Configuring SnapLock
You must install the SnapLock license, initialize the ComplianceClock, create and configure a SnapLock aggregate and volume, and mount the volume before you can commit files to WORM. - Committing files to WORM
You can use a command or program to commit files to WORM manually, or use the SnapLock autocommit feature to commit files to WORM automatically. - Committing Snapshot copies to WORM
You can use SnapLock for SnapVault to WORM-protect Snapshot copies on secondary storage. You perform all of the basic SnapLock tasks on the SnapVault destination. The destination volume is automatically mounted read-only, so there is no need to explicitly commit the Snapshot copies to WORM; therefore, creating scheduled Snapshot copies on the destination volume using SnapMirror policies is not supported.
- Mirroring WORM files
You can use SnapMirror to replicate WORM files to another geographic location for disaster recovery and other purposes. Both the source volume and destination volume must be configured for SnapLock, and both volumes must have the same SnapLock mode, Compliance or Enterprise. All key SnapLock properties of the volume and files are replicated. - Creating an audit log
You must create a SnapLock-protected audit log before performing a privileged delete or SnapLock volume move. The audit log records the creation and deletion of SnapLock administrator accounts, modifications to the log volume, whether privileged delete is enabled, privileged delete operations, and SnapLock volume move operations. - Using the privileged delete feature
You can use an audited privileged delete to delete Enterprise-mode WORM files during the retention period. You must be a SnapLock administrator to perform a privileged delete. - Using the Legal Hold feature
You can use the Legal Hold feature to retain Compliance-mode WORM files for the duration of a litigation. - Using the Event Based Retention (EBR) feature
You can use the SnapLock Event Based Retention (EBR) feature to define how long a file is retained after the occurrence of an event. - Moving a SnapLock volume
Starting in ONTAP 9.8, you can move a SnapLock volume to a destination aggregate of the same type, either Enterprise to Enterprise, or Compliance to Compliance. You must be assigned the SnapLock security role to move a SnapLock volume. - SnapLock APIs
You can use Zephyr APIs to integrate with SnapLock functionality in scripts or workflow automation. The APIs use XML messaging over HTTP, HTTPS, and Windows DCE/RPC. - Where to find additional information
You can learn more about the tasks described in this guide in Lenovo's extensive documentation library. - Contacting Support
You can contact Support to obtain help for your issue. - Notices
Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area.
Give documentation feedback