User's Manual

264
software
(FSE software)
The programs and data files that are included in the FSE package. Once installed, they actively
control the FSE implementation and provide functionality to its users. See also ”implementation
(FSE implementation)”.
system file
(FSE system file)
A temporary file, created by the FSE software, which contains information about the current
status of the FSE implementation. FSE system files are Fast Recovery Information, File System
Catalog transaction logs, Hierarchical Storage Manager lists, and the FSE disk buffer files.
tape media pool
(FSE tape media pool)
See ”media pool (FSE media pool)”.
tool
(FSE tool)
A command that communicates directly with FSE daemons/services and agents besides
Management Interface, designed for low-level modifications and more extensive monitoring
and troubleshooting tasks. FSE tools are only intended for use by experienced FSE users
(typically on request of FSE support personnel). Note that incorrect use of FSE tools can cause
data corruption. FSE tools are located in the directory /opt/fse/sbin/tools (on Linux
platform) or in the directory %InstallPath%\bin (on Windows platform).
Ultrium See ”LTO Ultrium”.
unreliable medium An FSE medium to which further writing is disabled, but from which FSE is still able to read
data. Its status is set to “unreliable” in the Resource Management Database automatically as
soon as the first write error is detected while the Back End Agent is writing data to the medium.
Usually, such errors occur because of an excessive use of the medium.
unusable medium An FSE medium which has been disabled for both writing to and reading from. Its status is set
in the Resource Management Database to “unusable” automatically as soon as the first read
error is detected while the Back End Agent is reading data from the medium. Usually, such
errors occur because of an extremely excessive use of the medium.
user (FSE user) A computer system user who uses one or more HSM file systems for managing data.
verified drive An FSE drive that is put back in operation after its problems have been resolved. This is done
by changing its status in the Resource Management Database to “online”. The online status is
set manually using the fsedrive command.
WORM file system A file system on which a file can be written only once, but can be read many times. A WORM
file system prevents both files and their metadata from being modified, regardless of their
access permissions. Consequently, it is not possible to remove files from directories or rename
them; it is only possible to add new files (as on a regular file system). Files and directory
operations are restricted to read-only after a period of time.