HP StorageWorks File System Extender Software V3.4 CLI reference (T3648-96013, October 2006)

2.2 NAME 15
In case of disaster, you can use the fserestore command to restore the complete
FSE state from such backup image.
The backed up items include entities that are shared among FSE clients in the FSE
implementation, as well as entities that belong to each particular FSE client. The
following entities are backed up:
• Global configuration files (omniORB.cfg, services.cfg, trace.cfg)
• Resource Management Database (RMDB)
• Configuration Database (CfgDB)
• File System Catalogs (FSCs)
• Fast Recovery Information (FRI)
Additionally, the log files on the FSE server are also backed up:
• FSE event log (renamed to fse_<YYYY><MM><DD>.log in the backup
image, where <YYYY><MM><DD> is the current timestamp)
• FSE error log (renamed to error_<YYYY><MM><DD>.log in the
backup image, where <YYYY><MM><DD> is the current timestamp)
• HSM file system logs (only if FSE server is part of a consolidated FSE
system)
Note:
User data on HSM file systems and the belonging Hierarchical Storage Man-
agement Databases (HSMDBs) are not backed up. If disaster occurs on a
particular HSM file system, you can use the inherent HSM file system recov-
ery functionality to recover from it. HSM file system recovery can be started
with the fserecover command. For more information, see the FSE user guide.
PREREQUISITES FSE backup uses logical volume snapshot technology to
keep the operation of FSE implementation almost unobstructed during the backup
window. To be able for the FSE backup to use this technology, all entities that are
HP StorageWorks File System Extender Software CLI reference