Table of ContentsView in Frames

How SnapLock autocommit feature works

The SnapLock autocommit feature enables you to commit all the files in a SnapLock volume to the WORM state automatically. In a new SnapLock volume, the autocommit feature is disabled by default. You can enable the autocommit feature on a SnapLock volume by using the vol options command.

You can set the autocommit period of a SnapLock volume in hours, days, months, or years. The minimum autocommit period that can be specified to commit the files to WORM state is two hours. However, the autocommit operation does not take place immediately when the autocommit period ends; instead, the specified period is the minimum amount of time for which the files that are not modified become eligible for locking. The autocommit operation might not follow the autocommit period instantly because of the additional processing needed to commit multiple files to the WORM state.

When you use the autocommit feature to commit a file to WORM, the value (file's ctime value plus volume autocommit period) is compared with the value of the system clock. If the system clock value is greater, the file is committed to WORM state.

Note: A file that is automatically committed to the WORM state gets a retention period equal to the volume's default retention period. However, if you explicitly change the atime value of the file before it is automatically committed, the file's retention date will be the atime value set by you.