User's Manual

HP StorageWorks File System Extender Software user guide 221
CAUTION: Resource Management Database is the most crucial component in the FSE implementation
and critical for recovery of other components, such as File System Catalogs and Fast Recovery Information.
Since RMDB can only be restored from FSE backup images, HP recommends that you define and follow a
backup policy that will keep data safety on the appropriate level.
Backup
Before you start using FSE backup feature, you need to become familiar with backup prerequisites and
course of the backup process, learn details about backup media management (if tape will be used as a
backup destination), and factors that you have to consider for defining an appropriate backup policy.
What is FSE backup?
FSE backup is a process that creates backup images with complete and consistent state of FSE components
located on the FSE server at a particular point in time. Such backup images can be used in emergency
situations to recreate data on the FSE server that has been damaged or destroyed.
The following components on the FSE server 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 following log files on the FSE server are also backed up:
• FSE event log (renamed to fse_YYYYMMDD.log in the backup image, where YYYYMMDD is the current
timestamp)
• FSE error log (renamed to error_YYYYMMDD.log in the backup image, where YYYYMMDD is the
current timestamp)
• HSM file system logs (only if FSE server is part of a consolidated FSE system)
FSE backup is initiated with the fsebackup command. It is an optimized process that does not obstruct
operation of the FSE implementation if it is well considered. Therefore, you need to plan your backup
strategy carefully, taking into account the prerequisites and the course of backup process.
Using fsebackup, FSE backup images can be created either on disk (local or remote disk volume or
share), on tape (FSE medium in the backup FSE media pool), or on both backup destinations.
Global configuration files on FSE server
and FSE clients
Linux specific
On Linux platform, global configuration
files are located in the directory
/etc/opt/fse.
Windows specific
On Windows platform, global
configuration files are located in the
directory %InstallPath%\etc.
The value of %InstallPath% depends
on the choice made in the FSE
installation process. It defaults to
C:\Program Files\Hewlett-Pac
kard\FSE.
Global configuration files are
customizable files that hold FSE
implementation-wide or FSE
client-wide configuration.
On FSE server, the following global
configuration files exist:
backup.cfg, drive.cfg,
library.cfg, omniORB.cfg,
services.cfg, trace.cfg.
On FSE clients, the following global
configuration files exist:
services.cfg, trace.cfg.
Note that some of the above files are
not backed up. For list of the global
configuration files that are backed
up, see section ”
What is FSE
backu
p?
” on page 221.
• Restore (applicable only to
FSE server)
(see ”
Restore” on page 230)
• New configuration from
scratch
FSE component Description Recovery method