
ibrix_datavalidation
Performs a data validation scan of a file system or subdirectory.
Description
To ensure that WORM and retained files remain unchanged, it is important to run a data validation
scan periodically. Circumstances such as the following can cause a file to change unexpectedly:
• System hardware errors, such as write errors
• Degrading of on-disk data over time, which can change the stored bit values, even if no data
is accessed
• Malicious or accidental changes made by users
A data validation scan computes hash sum values for the WORM, WORM-retained, and
WORM-hold files in the scanned file system or subdirectory and compares them with the values
originally computed for the files. If the scan identifies changes in the values for a particular file,
an alert is generated on the GUI. You can then replace the bad file with an unchanged copy from
an earlier backup or from a remote replication.
NOTE: Validation can only be run on file systems that are enabled for data retention. Only
WORM and WORM-retained files, including files under legal hold, are validated. Normal files
are not validated.
A legal hold locks the file and the data retention policy in place on the file system will be ignored.
For example, the expiration time does not apply to the file. A file can only be set to legally held
by command line. The file is then held WORM-retained until the legal hold is removed and then
the normal retention settings take effect.
The time required for a data scan depends on the number of files in the file system or subdirectory.
If there are a large number of files, the scan could take up to a few weeks to verify all content on
storage. A scheduled scan will quit immediately if it detects that a scan of the same file system is
already running.
A unique validation summary report is generated for each scan. The reports are located in the root
directory of the file system at {filesystem root}/.archiving/validation/history.
The report files are named <ID-n>-sum, such as 1-0.sum, 2-0.sum, and so on. The ID is the
task ID assigned by StoreAll software when the scan was started. The second number is 0 unless
there is an existing summary report with the same task ID, in which case the second number
increments to make the filename unique.
NOTE: The StoreAll .archiving directory does not appear when you run the ls -a command
on the root directory of the file system; however, it is visible when you cd into the directory and
use the ls -a command. Also, Linux commands such as cp work correctly when .archiving
is in a path or filename used in the command.
Synopsis
Perform a validation scan on the specified file system or subdirectory:
ibrix_datavalidation -s -f FSNAME [-d PATH]
Options
DescriptionOption
Specifies a subdirectory.-d PATH
Specifies a file system.-f FSNAME
52 StoreAll software commands
Kommentare zu diesen Handbüchern