How to manage WORM data
After creating SnapLock volumes, you can transition a file to the WORM state and set the retention date on the file, determine whether a file is in the WORM state, or extend the retention date of a WORM file.
- Transitioning data to the WORM state and setting the retention date
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 interactively or automatically. In addition, you must set the retention date for the file.
- Extending the retention date of a WORM file
A WORM file can remain in WORM state longer than the current retention date if you extend the retention date of the WORM file beyond that of the current retention date.
- Determining the WORM status of a file
You can check whether the files placed in a SnapLock volume are committed to the WORM state.
- What the WORM append file is
You can append data to a WORM append file. The WORM operations are done in 256-KB segments, so that when byte 256KB+1 is written, the previous segment automatically becomes immutable.
- Creating a WORM append file
The WORM append file procedure is used to create the SnapLock for SnapVault Compliance Log. The WORM append file works with chunks of 256-KB. As each chunk is filled, it is locked. The file must be made read-only for it to be locked in its entirety.
