How SnapVault maintains compliance SnapVault uses a SnapLock volume in which the log files are kept. This volume, called SnapLock for SnapVault log volume, is a standard WORM volume. SnapVault uses an append-only write operation to write to the log files. This allows accurate record keeping but does not allow previous events to be overwritten.
Configuring the log volumes of the SnapLock for SnapVault feature
A log volume for the SnapLock for SnapVault feature must be a SnapLock volume. The SnapLock volume can be a traditional volume or a flexible volume. All SnapVault log entries are created in the log volume. This is a system-wide option; therefore, a SnapVault operation on any SnapLock volume is logged to the log volume. However, you need to set this option for SnapVault transfers to SnapLock volumes to succeed.
Where the log files are kept
All SnapVault log files are kept in the log directory of the SnapLock for SnapVault log volume that you created and configured.
What files-transferred log files contain
A transfer log contains a header that describes the transfer and zero or more entries that describe the contents of the transfer.
Types of log entries recorded
All create, delete, modify, and rename operations are recorded in the transfer log files.
How log entries are created
Certain actions cause SnapVault to create a log entry type. The following table lists actions that cause SnapVault to create a log entry, the type of log entry created, and possibly a note about the action.
How to provide backup and standby protection using SnapMirror
By setting up a SnapMirror relationship between the SnapVault secondary storage system and a SnapMirror destination or NearStore system, you can provide backup and standby protection for the SnapVault secondary storage system data.