Setting the time delay before automatically committing to the WORM state

You can set a global option that determines how long a file must remain unchanged in the SnapLock volume before it is committed to the WORM state.

Step

To set the autocommit time delay, enter the following command: options snaplock.autocommit_period none|(count|h|d|m|y)
autocommit_period is the time delay in hours, days, months, or years.
Example
The following example sets the autocommit period to 24 days. options snaplock.autocommit_period 24d

Note: You can turn off the autocommit feature by setting the time delay to none.

File access before and after autocommit

The following example shows a file with read-write permissions and autocommit set.

$ stat *
  File: "new.txt"
  Size: 11 Blocks: 0 IO Block: 8192   Regular File
Device: 1eh/30d Inode: 1512 Links: 1
Access: (0664/-rw-rw-r--) Uid: (15883/  djv) Gid: ( 30/    engr)

The following example shows how permissions become read-only after the autocommit period has elapsed.

$ stat *
  File: "new.txt"
  Size: 11 Blocks: 0 IO Block: 8192   Regular File
Device: 1eh/30d Inode: 1512 Links: 1
Access: (0444/-r--r--r--) Uid: (15883/ djv) Gid: ( 30/ engr)

After the SnapLock retention period has elapsed, no changes will be made to the file. The file will continue to look as it does in this example. If you want to delete the file, you must manually change permissions to read-write after the retention period has ended. There is no automatic reset feature.

Parent topic: How SnapLock automatically commits files to WORM state