HP StoreAll Storage - Manual (Page 297)

Saving and importing custom metadata and audit information
Use the following procedures to save, or export, custom metadata that is stored only in the Express
Query database and not in the files themselves. You can also import the metadata if you need to
recreate the Express Query database on the file system from which you exported the metadata. If
you are recovering a complete file system with NDMP backup or a supported non-NDMP backup
application, you do not need to import the metadata, but you may want to import the custom
metadata and audit history data if you restored the files from a backup to an existing file system
with Express Query enabled as described in the section above. The Express Query database and
the metadata are included in a full file system backup and thus it is recovered with the file system.
Saving custom metadata for a file system
Use the perl script MDExport to save custom metadata in a CSV file. You can then use the file
later on to import the metadata. The script has the following syntax:
MDExport.pl [--help|?] --dbconfig /usr/local/Metabox/scripts/startup.xml
--database --outputfile --user ibrix-eq [--verbose]
The options specify the following:
Description Options
The metadata configuration file. Use only this path and file name. --dbconfig
/usr/local/Metabox/scripts/startup.xml
The database containing the metadata. is the name of
the file system. --database
The CSV output file used to save the metadata. --outputfile
The username for accessing the database. Use only the “ibrix-eq”
username. --user ibrix-eq
Use perl to invoke the script. For example:
perl /usr/local/ibrix/bin/MDExport.pl --database ibrixFS --user ibrix-eq
--dbconfig /usr/local/Metabox/scripts/startup.xml --output
/home/mydir/save.csv
This command exports metadata from the ibrixFS file system and generates the output file
save.csv
in the /home/mydir directory. The CSV file contains a row for every custom attribute.
The first row is a file format version identifier. As of 6.5, the format is 2. The remaining
rows are formed by the following list of comma separated fields:
•
: The path name
•
: The key of the (key, value) pair of the custom metadata
•
: The value part
•
: The timestamp in seconds since UNIX epoch of the last change done on the
custom attribute
•
: Control/identification fields used internally by Express Query (never
modify these fields)
Saving audit journal metadata
The ibrix_audit_reports command saves audit data from Express Query on a specific file
system. The data is placed in a CSV file. The command has the following syntax:
ibrix_audit_reports -t SORT_ORDER -f FILESYSTEM [-p PATH] [-b BEGIN_DATE]
[-e END_DATE] [-o class1[,class2,...]]
For example:
Managing the metadata service 297