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

2.2 NAME 14

2.2 NAME

fsebackup:

Create backup image with complete FSE server state.

2.2.1 SYNOPSIS

fsebackup [{–f | ––ﬁle} BackupFileName [– –nomedia]]

fsebackup [{–f | – –ﬁle} BackupFileName] [{–m | – –medium} Barcode [–i |

– –init]]

fsebackup {–h | ––help}

fsebackup {–v | ––version}

2.2.2 DESCRIPTION

Each FSE command communicates with the FSE processes through the Manage-

ment Interface (fse–mif). To execute an FSE command, the Management Interface

must be running. If the connection to the Management Interface fails, check its

status by running the fse ––status command. In case the Management Interface is

not running, start it with the fse – –start command. Additionally, fsebackup also

requires Partition Manager processes (fse–pm) for all conﬁgured FSE partitions to

be running. This can be checked with the fsesystem or fsepartition command. If

tape will be used as a backup destination, Resource Manager (fse–rm) must also

be running. You can check its status with the fse command.

After a successful command execution fsebackup notiﬁes the FSE administrator

with a suitable message, which is printed to the standard output stream (stdout).

If there was an error during the command execution, an appropriate error message

is printed to the standard error stream (stderr).

BACKUP CONCEPTS fsebackup creates backup image with consistent state

of FSE databases and system ﬁles on the FSE server at a particular point in time.

Backup image can be stored on disk (local or remote disk volume or share), on

tape (FSE medium in the backup FSE media pool), or on both backup destinations.

HP StorageWorks File System Extender Software CLI reference