Storage Management
164
Titan SiliconServer
•
Lax WORM file systems can be reformatted and so should only be used for testing
purposes. Should a lax WORM file system need to be deleted, it must first be reformatted
as a non-WORM file system.
•
Strict WORM file systems cannot be deleted or reformatted and should be used once
strict compliance measures are ready to be deployed.
Creating a WORM file system
Designating a file system as WORM is done when a file system is created. For more information,
see "
To Create a Silicon File System
".
Any existing non-WORM file system can be reformatted as a WORM file system. Reformatting a
file system to use a different file system type, must be done at the CLI. For detailed information
on this process, run
man format
at the CLI.
Retention Date
Before marking a file as WORM, designate its retention date. To configure the retention date, set
the file's "last access time" to a specific time in the future. The "last access time" can be set
using the Unix command
‘touch’
, e.g.
touch -a MMDDhhmm[YY] ./filename.
Should the
retention date be less than or equal to the current time, the retention date will never expire.
After a file is marked as WORM, file permissions cannot be altered until the file reaches its
retention date. Once a WORM file reaches its retention date, its permissions can be changed to
allow read-write access. When write access is granted, the file can be deleted. However, the
contents of the file will still remain unavailable for modification.
Marking a file as WORM
Once the retention date has been set, a file can be marked as WORM. To mark a file as WORM,
configure the permissions of the file as read-only. To do this from a Unix client, remove the write
attribute permissions. From a Windows client, mark the file as read-only through the file’s
properties.
