CLI Reference Guide

2.3 NAME 24

Partition Manager processes (fse–pm) for all conﬁgured FSE partitions must be

running. This can be checked with the fsesystem command.

After successful command execution, fsebak notiﬁes the FSE administrator with

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

was an error during command execution, an appropriate error message is printed

to the standard error stream (stderr).

ACHIEVING THE FSE DATABASE CONSISTENCY fsebak – –suspend

follows for each running Partition Manager the following procedure:

• block the incoming job requests in Partition Manager;

• make the corresponding HSMDB and FSC incorporate all changes from

their transaction logs into the main database ﬁles;

• write temporary ﬁles hsm.ref and fsc.ref with references to HSMDBs and

FSCs for use with the – –continue option;

• report action success or failure.

Note:

Contents of hsm.ref and fsc.ref ﬁles should not be directly altered in any way.

If all these steps are successfully completed, duplicate copies of HSMDBs and

FSCs can be made.

RESUMING NORMAL FSE SYSTEM OPERATION fsebak – –continue

StatusCode follows for each running Partition Manager the following procedure:

• read references to HSMDBs and FSCs from ﬁles hsm.ref and fsc.ref ) and

delete these two ﬁles;

• start accepting incoming job requests in Partition Manager and resume nor-

mal operation.

If the value 0 (zero) is used in place of the StatusCode argument, all old transaction

log ﬁles of HSMDBs and FSCs are removed, as the assumption is they will not be

needed any more. If any other value is used as the StatusCode, these transaction

logs are preserved for a potential future use.

HP StorageWorks File System Extender Software CLI reference