2.1 NAME

4

all. FSE administrator has to know exactly what he is doing when using this com- mand.

The command is used to perform these FSE administrator’s tasks:

start or shut down FSE processes to enable or cease the FSE implementation (FSE server, FSE client) operation,

restart FSE (server, client) processes in case of problems,

print status information for the configuration–independent FSE daemons (services) running in the FSE implementation (FSE server, FSE client),

on Windows systems, configure mount points for HSM file systems, mount or unmount HSM file systems,

on Windows systems, dismount a newly formatted volume, enable or dis- able Limited Access Mode for a particular HSM file system,

on Windows systems, enumerate all local volumes and report their status with respect to the FSE implementation.

FSE PROCESSES Core FSE components, as for fse command, are running FSE processes, that are responsible for proper FSE operation. There are two groups of FSE processes: configuration–independent and configuration– dependent. The configuration–independentFSE processes, also called FSE daemons (services), allow FSE software to operate and intercommunicate. The configuration–dependentFSE processes control a single configured FSE resource. FSE administrator may configure more than one resource of the same kind, so there can be several FSE processes of the same kind running simultaneously. Cur- rently, the only resources that are controlled by their own processes are FSE partition and FSE library.

CONSOLIDATED AND DISTRIBUTED FSE IMPLEMENTATIONS It is possible to either set up FSE on a consolidated system or distribute its functionality across one FSE server and an arbitrary number of FSE clients. In first case, all FSE processes are running on the same system, in the other some of them only on FSE server as FSE server processes (marked with S character), some only on

HP StorageWorks File System Extender Software CLI reference