6.5 HP StoreAll OS User Guide

If the path name limit is exceeded, the path name:
• Appears in audit report logs in the format of “<TRUNCATED>/” + <last 2,548 characters of
the path name>.
• Does not get collected for file system reports.
• Appears empty in REST API and Express Query Windows Search Integration query results.
This affects the JSON output depending on the requested query mode:
◦ For the default/bypath query mode, REST API will not display the path name and its
corresponding attributes in the JSON output (essentially, the entry is omitted from JSON).
◦ For the bypoid query mode, REST API will display the POID key of the corresponding
path name and its non-empty attributes in the JSON output. As a result, the system::path
attribute is not displayed because it is empty.
The truncated path names are fixed in the database when the online metadata synchronizer is run
(scheduled using the ibrix_archiving command). Be aware that the default schedule for the
synchronizer is once a week, unless you change it to run more frequently. Or, if you have disabled
the online synchronizer to preserve I/O resources, it will not run at all.
One way to check for path name limits is to monitor the log file
(/usr/local/ibrix/log/ajscanner_truncation.log), which includes the truncated path names. You
may be able to identify the source application or user creating these path names and plan to run
the online synchronizer.
Truncated path names in audit logs can also occur when setting a file to legal hold. If you set a
file to legal hold and Express Query auditing is turned on for this operation, the file name may be
truncated when viewing the file in the audit report logs.
Filesystem Metadata Cleaner
The Filesystem Metadata Cleaner is a daily operation that runs at 1:30 a.m. (this is the default
time but you can change it). The cleaner ensures that the Express Query File Objects table is
synchronized with the file system for operations such as Autocommit and WORM+Retained files.
The cleaner also removes old Express Query metadata to avoid consuming too much user space
on the StoreAll file system.
The Filesystem Metadata Cleaner performs the following tasks for each Express Query-enabled file
system:
• Audit log expiration
• Auto commit files
• Retention expiration
• Garbage collector
• FileDeleteTime table cleaner
• AttributeCleaner and InFluxFileLifeTime tables cleaner
• Corrupt events cleaner
The cleaner is started as an active subsystem in the Fusion Manager, so it will only run in the active
Fusion manager.
Audit log expiration
You can set an expiration policy on each file system to define how long audit logs should be
retained. If the date you set has passed when the Filesystem Metadata Cleaner is run, the audit
logs are deleted.
NOTE: This task is only executed if the file system is mounted.
306 Express Query