Table of ContentsView in Frames

Transitioning data to the WORM state

You must transition a file from the writable to read-only state in the SnapLock volume for the file to be committed to a WORM state. You can transition data to the WORM state manually or automatically and set the retention date for the file.

About this task

When you commit a file to WORM state, volume ComplianceClock time is written to the ctime field of the file. The volume ComplianceClock is used for calculating the retention period of a file.
Note: The ctime value is different from the atime value that is used as the retention date of the file.

Steps

  1. Set the retention date using the command or program available to the file access protocol (CIFS, NFS, and so on) and client operating system you are using.
    Example
    In a UNIX shell, use the following command to set the document.txt file with a retention date of 21 November 2020:touch -a -t 202011210600 document.txt
  2. Commit the document.txt file to the WORM state by using the following command:chmod -w document.txt
    Note: The last accessed timestamp of the file at the time it is committed to the WORM state becomes its retention date unless it is limited by the minimum or maximum retention period of the SnapLock volume. If no retention date was set for the file, the default retention period of the SnapLock volume is used. The file's retention date is stored in the atime field. The option no_atime_update is always set to on for SnapLock volumes. Therefore, atime is not updated when files are accessed.