Filter
Top Products
Chapter 2 HPSS Planning
118 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
PVL Activities. This metadata file stores individual PVL activity requests such as individual tape
mounts. Depending on howmany concurrent I/O requests are allowed to flow through the Storage
Server and PVL at any given time, this metadata file should not grow beyond a few hundred
records.
2.10.2.10 PVR Metadata
The PVR is the primary user of one SFS metadata file (the default SFS filenames are shown in
parentheses):
• Cartridges (cartridge_3494 for 3494 PVR, cartridge_3495 for 3495 PVR, cartridge_stk for STK
PVR, cartridge_stk_rait for STK RAIT PVR, cartridge_aml for AMLPVR, cartridge_operator for
Operator PVR, cartridge_lto for LTO PVR)
The STK RAIT PVR cannot be supported at this time since STK has not yet made RAIT
generally available.
Cartridges. The cartridge metadata file contains a single record for each cartridge managed by the
PVR. Therefore, the number of records will equal the number of tape cartridges injected into this
PVR. If multiple PVRs are used, eachPVR should use a separate SFS file tostore cartridge metadata.
2.10.2.11 Mover Metadata
The Mover is the primary user of one SFS metadata file (the default SFS filename is shown in
parentheses):
• Mover Devices (moverdevice)
Mover Devices. This metadata file contains a single record for each Mover device that is defined,
including both disk and tape devices. All Mover devices should be defined in a single SFS file.
2.10.2.12 Migration/Purge Server Metadata
The MPS Server is the primary user of the following SFS metadata files (the default SFS filenames
are shown in parentheses):
• Threshold Policies (sclassthreshold)
• Migration/Purge Checkpoints (mpchkpt.#, where # is the storage subsystem ID)
Threshold Policies. Each storage subsystem specific storage class threshold requires a record in this
file. The maximum number of records is the product of the number of storage subsystems and the
number of storage classes. This file name is configured on the HPSS Global Configuration window.
Migration/Purge Checkpoints. MPS creates a single checkpoint record in this file for each disk
storage class which is configured for migration (i.e. with a migration policy). This checkpoint
record is used to round-robin the starting hierarchy for each disk migration run. This file name is
configured on the Migration/Purge Server Configuration window.