6.3 HP StoreAll Storage File System User Guide (TA768-96093, June 2013)

Restore to an existing file system that has Express Query enabled
To restore a backup to an existing file system that has Express Query enabled:
1. Disable the express query feature for the file system, including the removal of any StoreAll
REST API shares. Disable auditing feature before you disable the express query feature.
a. To disable auditing, enter the following command:
ibrix_fs -A [-f FSNAME] -oa audit_mode=off
b. Remove all StoreAll REST API shares created in the file system by entering the following
command:
ibrix_httpshare -d -f <fs_name>
c. To disable the express query settings on a file system, enter the following command:
ibrix_fs -T -D -f FSNAME
2. Delete the previously existing metadata database:
rm -Rf <mountpoint>/.archiving/database
3. Delete the previously existing archive journal files that the file system creates for Express Query
to ingest:
rm -Rf <mountpoint>/.audit/*
4. Restore the backed up file system to this file system, overwriting existing files.
5. Re-enable Express Query on the file system, either in the Management Console or by the CLI
command:
ibrix_fs -T -E -f <FSNAME>
6. (Optional) Enable auditing, using the ibrix_fs -A [-f FSNAME] -oa … CLI command
or in the Management Console.
7. (Optional) Create REST API shares. See “Using HTTP” (page 114).
Express Query re-synchronizes the file system and database by using the restored database
information. This process might take some time.
8. Wait for the metadata resync process to finish. Enter the following command to monitor the
resync process for a file system:
ibrix_archiving -l
The status should be at OK for the file system before you proceed. See the ibrix_archiving
section in the HP StoreAll Storage CLI Reference Guide for information about the other states.
Saving and importing file system metadata
Use the following procedures to save, or export, metadata that is stored only in the Express Query
database and not in the files themselves. You can then import the metadata later on a CRR target.
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. 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 <dbname> --outputfile <fname> --user ibrix [--verbose]
Managing the metadata service 219