User's Manual

226 Backup, restore, and recovery
NOTE: HP recommends that you perform your backups on a daily basis.
Starting FSE backup
The fsebackup command
To start FSE backup, run the fsebackup command on the FSE server. After fsebackup invocation, a
backup job is created in the FSE implementation, which performs all steps of the backup process. Common
synopsis of the fsebackup command is the following:
The options --file and ---nomedia determine which backup destination will be used to store FSE
backup image:
• If neither option is specified, the backup image will be copied to a backup FSE medium.
• If options --file and --nomedia are specified, the backup image will be copied to a local or
remote disk or share.
• If only the option --file is specified, the backup image will be copied to a local or remote disk or
share, as well as to a backup FSE medium.
BackupFileName can be absolute pathname, relative pathname, or filename. If . (dot) is specified
instead of filename, the filename is automatically constructed from name of the host on which fsebackup
is run and the current timestamp. The following template is used for automatic generation:
The .tar.bz2 extension is also appended to the filename if the specified filename does not already
include it.
When tape or both backup destinations are selected, additional option --medium selects a specific
backup FSE medium to which the backup job will copy the backup image. The option --init causes this
backup FSE medium to be initialized before copying, if free storage space on it is insufficient.
IMPORTANT: If both backup destinations are selected (the --file option is specified without the
additional --nomedia option), and the backup image cannot be copied to tape for some reason (FSE
media pool is not configured, all backup FSE media are full, the backup FSE medium specified by the
options --media Barcode is full), the backup session as a whole will fail. However, the actual backup
process will partially succeed and the backup image will be copied to disk. In the opposite case, when the
backup image cannot be copied to disk for some reason, the backup process will fail completely and the
backup image will neither be copied to tape.
For additional information on the fsebackup command, see the fsebackup man page.
Examples of backing up to disk
The FSE backup image will be stored to the share \\backup–server\backup_share under the name
backup_image.tar.bz2. In this example, the FSE server is running on a Windows host:
The FSE backup image will be stored on the file system /mnt/backup under the name
backup_image_file.tar.bz2. In this example, the FSE server is running on a Linux host:
fsebackup [––file BackupFileName [––nomedia]]
fsebackup [––file BackupFileName] [––medium Barcode [––init]]
HostName–YYYYMMDD–hhmmss.tar.bz2
C:\>fsebackup --file \\backup–server\backup_share\backup_image.tar.bz2 --nomedia
# fsebackup --file /mnt/backup/backup_image_file.tar.bz2 --nomedia