File System Event | A daemon (service) on the FSE client which receives notification about mount events for the |
Manager | HSM file system and triggers the startup of the appropriate Hierarchical Storage Manager. The |
| File System Event Manager process name is |
forced release | Release of all files on an HSM file system, which are on the release candidate list, regardless of |
| their retention time and file size. Forced release is triggered when the critical watermark of |
| usage is reached on the HSM file system. The process is stopped in the moment when the high |
| watermark on the HSM file system is reached. See also ”release”. |
formatting | A process that partitions a medium into medium volumes, according to the parameters |
| specified in the FSE media pool configuration. During formatting all data on the medium is |
| erased. If an FSE medium contains valid FSE user data and you want to format it, you must use |
| forced formatting. |
Full Access Mode | One of the two HSM file system filter operational modes. When HSM file system filter is |
(FAM) | operating in Full Access Mode for a particular HSM file system, you are allowed to make |
| changes to the data located on the HSM file system, and use all the HSM file system |
| functionality that the FSE system provides. For example, you can create, rename, move or delete |
| directories and files, and change their data or metadata. In this mode, all data movement |
| processes (migration, release, recall, deletion) can be executed – by being either triggered |
| explicitly or started according to the configured FSE partition policies. See also ”Limited Access |
| |
good medium | A usable FSE medium in its fully operational state. In this state, the medium may have any of the |
| following statuses: uninitialized, free, empty, in use, full. This state lasts as long as |
| the medium is in a good condition, that is, no write and read errors are detected while writing |
| data to and reading data from the medium. |
Hierarchical Storage | A database with migration candidate and release candidate lists for files on the HSM file |
Management | system. Each FSE partition has its own Hierarchical Storage Management Database. |
Database (HSMDB) |
|
Hierarchical Storage | A file which contains transaction information for Hierarchical Storage Management Databases. |
Management | It is designed to increase the database robustness. HSMDB journals contain information about |
Database journal | already applied and pending database transactions. Hierarchical Storage Management |
| Database journals are located in the directory |
| /var/opt/fse/part/PartitionName/hsm/journal (on Linux platform) or in the |
| directory %InstallPath%\var\part\PartitionName\hsm\journal (on Windows |
| platform). |
Hierarchical Storage | A part of the FSE client that handles file system events relevant for the FSE implementation and |
Manager (HSM) | enforces migration, release, and recall policies. The Hierarchical Storage Manager process |
| name is |
Hierarchical Storage | A list of files, maintained by the Hierarchical Storage Manager, which are candidates for |
Manager list (HSM | migration or release. HSM lists are: a dirty file list (the list of changed files), a migration |
list) | candidate list, and a release candidate list. |
high watermark | A |
| value is reached, a regular release process is started for all files that are on the Hierarchical |
| Storage Manager's release candidate list and that have passed their migration or recall |
| retention period, and are larger than the defined MinFileSize. |
host | A computer system that hosts either a consolidated FSE system, an FSE server, or an FSE client. |
(FSE host) |
|
hot fix | A package with updated FSE binaries, FSE configuration files, or other FSE system files that are |
(FSE hot fix) | applied to the FSE implementation at a specific site, in order to solve one or more problems |
| reported by an FSE customer. |
HP StorageWorks File System Extender Software user guide 313