6.5 HP StoreAll OS User Guide

Auto commit files
NOTE: This task only applies to retention-enabled file systems.
Use the auto-commit feature to automatically move a file to a WORM+Retained state when the
defined time period has passed and no operations have occurred against the file. If a file operation
occurs before the defined time period has passed, that will also transition the file to
WORM+Retained. The auto-commit feature just ensures that the transition will occur with or without
a file operation.
NOTE: To ensure the most complete and current information is included in the query results, HP
recommends that you wait until the daily Filesystem Metadata Cleaner task has completed. This
task, which runs by default every day at 1:30 a.m., transitions files from Normal to WORM+Retained
and from WORM+Retained to WORM. If you query for files before this task completes, the result
may not include the latest WORM-related information.
The Auto Commit files task is only executed if:
• Auto-Commit is enabled for the file system.
• The file system is currently mounted.
Retention expiration
NOTE: This task only applies to retention-enabled file systems.
The RetentionExpiration task searches for retained files that have a retention period that has expired.
NOTE: This task is only executed if the file system is mounted.
Garbage collector
This task triggers an Express Query clean up function that deletes old, internal database metadata.
FileDeleteTime table cleaner
This task uses the same Audit Log Expiration Policy to delete rows from the FileDeleteTime table.
Each row in the table refers to a deleted file and the timestamp of this operation. The default Audit
Log Expiration Policy value is 1 day. This means files that were deleted in the past 24 (or more)
hours are deleted from the table.
AttributeKeyValue (AKV) and InFluxFileLifeTime (IFFLT) tables cleaner
When files are deleted, any custom metadata (CMD) assigned to those files are purged by this
task. The AKV table contains the CMD and the IFFLT table contains the time when the file was
deleted.
Corrupt events cleaner
The StoreAll system generates events for each file operation. These events are used as input to
reflect file metadata in the Express Query database and are user files that are consumed by services.
These events may contain corrupted data and must be saved for later debugging. Corrupt event
files are automatically moved to
<filesystem_mount_point>/.archiving/debug_event_files. Files that are older than
60 days are deleted by the Corrupt Events Cleaner task.
Filesystem Metadata Cleaner 307