The command is used to perform these FSE administrator’s tasks:
•start up or shut down FSE processes to enable or cease the FSE system (FSE server, FSE client) operation,
•restart FSE (server, client) processes in case of a trouble,
•print status information for the configuration–independent FSE processes (FSE daemons) running on FSE system (FSE server, FSE client),
•prepare the FSE system for the restore process,
•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.
FSE PROCESSES Core FSE components, as for fse command, are run- ning 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 dae- mons, allow FSE software to operate and intercommunicate. The configuration– dependent FSE processes control a single configured FSE resource. FSE admin- istrator may configure more than one resource of the same kind, so there can be several FSE processes of the same kind running simultaneously. Currently, the only resources that are controlled by their own processes are FSE partition and FSE library.
STAND–ALONE AND DISTRIBUTED FSE SYSTEMS It is possible to ei- ther set up an FSE system on a stand–alone machine 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 each FSE client as FSE client processes (marked with C character) and some on both/all (marked with S+C characters).
Configuration–independent FSE processes – FSE daemons are:
