Command Reference Guide

2.3 NAME 18

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, the

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’s 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 HSMDB and

FSC for use with the – –continue option;

• report action success or failure.

Note:

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

If all these steps were successfully completed, duplicate copies of HSMDB and

FSC can be made. Usually they are created with the fsebackup command. See

the fsebackup man page for details.

RESUMING A NORMAL FSE SYSTEM OPERATION fsebak – –continue

StatusCode follows for each running Partition Manager the following procedure:

• read references to HSMDB and FSC 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.

File System Extender 3.2 Command Line Reference