The value of the Equipment Type field of the Master Configuration File (mcf) identifies devices and device configurations within the Oracle Hierarchical Storage Manager and StorageTek QFS Software. Equipment types are specified as two-character codes. This glossary lists the codes for quick reference when working with the samples or when interpreting an existing mcf (for full details see the mcf(4) man page).
For convenience, the codes are divided into two sections and then listed alphabetically:
This section describes all of the equipment codes that you normally need: the generic equipment codes (rb, tp, and od) and codes for identifying network-attached library interfaces, archival disk volumes, cloud resources, and the Oracle HSM historian.
The generic equipment codes rb, tp, and od are the preferred equipment type codes for all SCSI-attached libraries, tape drives, and optical disk devices. When you specify a generic equipment type, Oracle HSM can automatically set the correct type based on SCSI vendor codes.
Cloud media, the abstract media type that organizes cloud resources into logical media volumes suitable for archiving. Oracle HSM labels each volume with a 31-character volume serial number (VSN) of the form nameNumber, where:
name is the customer-defined string of 4 to 20 alphanumeric characters that identifies the logical library (type cr) that owns the media. See "Create a Cloud Library Parameter File".
Number is a randomly generated number in the range [0000000-9999999].
For additional information, see the cloud (7) and sam-cloudd (1m) man pages.
A cloud library, the abstract equipment type that manages cloud media (volumes of type cl) by emulating a network-attached tape library with a configurable number of drives.
Cloud libraries support AES-256 symmetric-key encryption.
A parameter file defines the characteristics of the equipment, including the name parameter value that prefixes and uniquely identifies the type cl volumes that belong to the library. For instructions on creating these files, see "Create a Cloud Library Parameter File".
For additional information, see the cloud (7) and sam-cloudd (1m) man pages.
A disk-based file system that the Oracle HSM software uses as an archival volume. UFS, ZFS, QFS, and NFS file systems can serve as disk archives.
Disk volumes and volume serial numbers (VSNs) are defined in the /etc/opt/SUNWsamfs/diskvols.conf file. See "Configure Oracle HSM Hosts to Use Disk Volumes" and the diskvols.conf (4) man page.
Where XXX is an integer in the range [0-127], a striped group of disk devices that is part of an ma disk-cache family set.
The Oracle HSM historian, an optional, virtual library that maintains a media catalog, but has no associated hardware. Used for tracking exported media.
A high-performance QFS file system that maintains file-system metadata on one or more dedicated mm disk devices. File data resides on separate md, mr, or gXXX data devices.
A disk device that stores file data for an ma file system or data and metadata for an ms file system. md devices store file data in small, 4-kilobyte Disk Allocation Units (DAUs) and large, 16-, 32-, or 64-kilobyte DAUs. The default DAU is 64-kilobytes.
A disk device that stores file-system metadata for a high-performance ma file system.
A disk device that stores file data for an ma file system. mr devices store file data in large, fully adjustable Disk Allocation Units (DAUs) that are multiples of 8 kilobytes in the range 8-65528 kilobytes. The default DAU is 64 kilobytes.
A Oracle HSM file system that maintains file-system metadata on the same devices that store file data.
Any SCSI-attached optical disk. Oracle HSM sets the appropriate equipment type automatically using the SCSI vendor code.
An abstract media type that distinguishes foreign media from Oracle HSM file system media. Used when migrating files from a foreign file system to an Oracle HSM file system.
The of media type does not identify a physical equipment type. Never specify it in a master configuration file (mcf).
Any SCSI-attached tape library. Oracle HSM sets the appropriate equipment type automatically using the SCSI vendor code.
The SAM-Remote pseudo-device. In the Master Configuration File (mcf), the corresponding Equipment Identifier field has to contain the path to the pseudo-device (such as /dev/samrd/rd2). The corresponding Family Set field has to contain the hostname of the SAM-Remote server.
A SAM-Remote client system. In the Master Configuration File (mcf), the corresponding Equipment Identifier field has to contain the path the SAM-Remote client-configuration file for the client. The corresponding Family Set field has to contain the family set name of the server. The Additional Parameters field must contain the full path to the client's library catalog file.
An Oracle StorageTek ACSLS interface to a network-attached library. In the Master Configuration File (mcf), the corresponding Equipment Identifier field has to contain the path to the parameters file for the ACSLS interface. For more information, see the stk(7) man page.
A SAM-Remote server. In the Master Configuration File (mcf), the corresponding Equipment Identifier field has to contain the path to the SAM-Remote server-configuration file. The corresponding Family Set field has to contain the family set name of the server, which must match the name used in the Family Set field of the mcf on the client.
An abstract media type that distinguishes Oracle StorageTek T10000 and LTO volumes that are in Linear Tape File System (LTFS) format from volumes that contain Oracle HSM archive files.
The tf media type does not identify a physical equipment type. Never specify it in a master configuration file (mcf).
Any SCSI-attached tape drive. Oracle HSM sets the appropriate equipment type automatically using the SCSI vendor code. No, however, that if you do use more specific equipment codes such as li and ti, you must do so consistently. If you specify li (LTO) tape equipment in the mcf file, for example, you cannot refer to the same equipment as tp equipment in the archiver.cmd file
An abstract media type that distinguishes foreign media from media controlled by Oracle HSM software.
The equipment types listed in this section are also supported.
Note that, in most cases, Oracle recommends identifying SCSI-attached libraries, tape drives, and optical disk devices using the generic equipment types rb, tp, and od. The generic equipment types tell Oracle HSM to identify the hardware dynamically, using SCSI vendor IDs. The type codes below are essential when migrating from one media type to another and may sometimes be useful for management purposes. But using them in a Master Configuration File (mcf), for example, hard-codes a static equipment configuration that may, at some point, no longer match the actual hardware.
A Sun 1800, 3500, or L11000 tape library.
A Sony AIT-4 or AIT-5 tape drive.
A Cygnet optical disk library.
A StorageTek D3 tape drive.
A Sony DMF library.
A DocuStore or Plasmon optical disk library.
A DAT 4-mm tape drive.
An Exabyte X80 library.
A Fujitsu M8100 128-track tape drive.
An HP SL48 or SL24 library.
An Hewlett Packard L9-/L20-/L60-series library.
An IBM 3570 tape drive.
An IBM 3570 media changer.
An IBM 3584 tape library.
An LTO-3 or later tape drive.
A Digital Linear Tape (DLT), Super DLT, or DLT-S4 tape drive.
A Metrum library.
An IBM Multi Function optical drive.
A 5.25-in erasable optical drive.
A 12-in WORM drive.
An Overland Data Inc. Neo Series tape library.
A Plasmon D-Series DVD-RAM library.
A Qualstar 42xx, 62xx, or 82xx library.
A StorageTek SL3000 library.
An Oracle StorageTek 97xx series library.
A StorageTek 9490 tape drive.
A StorageTek T9940 tape drive.
A StorageTek 9840C or later tape drive.
A Spectra Logic or Qualstar tape library.
A StorageTek 3480 tape drive.
A StorageTek T10000 (Titanium) tape drive.
A Metrum VHS (RSP-2150) tape drive.
A 5.25-in optical WORM drive.
An Exabyte (850x) 8-mm tape drive.