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

2.2 NAME 17
databases, and then the transaction log files are removed. This action
achieves the required consistency of HSMDBs.
3. Transaction log files of File System Catalogs (FSCs) are committed to the
main databases. This action achieves the required consistency of FSCs.
4. Snapshots of the volumes with FSE databases and system files are created.
5. FSE server is resumed. Operation of all running Partition Managers is un-
blocked so that Partition Managers can process existing job requests and
accept new ones.
6. Backup data is collected, archived, and compressed into a single backup
image file, which is temporarily stored in the FSE disk buffer storage space.
On all supported platforms, backup image files use the .tar.bz2 file format.
7. According to the specified backup destination, the backup image is copied
to disk (local or remote disk volume or share), tape (FSE medium in the
backup FSE media pool), or both.
8. Transaction log files of File System Catalogs (FSCs), which were commit-
ted in step 3, are removed.
9. Snapshots of disk volumes are removed.
Note:
You can configure a regular cron job (on Linux systems) or schedule a task
(on Windows systems) to periodically run FSE backup.
ACTIVITY LOGGING fsebackup reports its progress to the FSE backup log.
To figure out the required backup window, consult the FSE event log. You can
determine the backup start and stop times from a previously run backup session.
Errors encountered during backup process are reported to the FSE error log. For
location and names of log files, see section FILES.
BACKUP CONFIGURATION On Linux systems, before starting backup, you
must check parameters in the backup configuration file and modify them, if
needed. Backup configuration file is named backup.cfg and located on the FSE
server (see section FILES). Configurable parameters and their default values are
the following:
HP StorageWorks File System Extender Software CLI reference