Computer Drive User Manual
Table Of Contents
- Chapter 1. HPSS 7.1 Configuration Overview
- Chapter 2. Security and System Access
- Chapter 3. Using SSM
- 3.1. The SSM System Manager
- 3.2. Quick Startup of hpssgui
- 3.3. Configuration and Startup of hpssgui and hpssadm
- 3.4. Multiple SSM Sessions
- 3.5. SSM Window Conventions
- 3.6. Common Window Elements
- 3.7. Help Menu Overview
- 3.8. Monitor, Operations and Configure Menus Overview
- 3.9. SSM Specific Windows
- 3.10. SSM List Preferences
- Chapter 4. Global & Subsystem Configuration
- 4.1. Global Configuration Window
- 4.2. Storage Subsystems
- 4.2.1. Subsystems List Window
- 4.2.2. Creating a New Storage Subsystem
- 4.2.3. Storage Subsystem Configuration Window
- 4.2.3.1. Create Storage Subsystem Metadata
- 4.2.3.2. Create Storage Subsystem Configuration
- 4.2.3.3. Create Storage Subsystem Servers
- 4.2.3.4. Assign a Gatekeeper if Required
- 4.2.3.5. Assign Storage Resources to the Storage Subsystem
- 4.2.3.6. Create Storage Subsystem Fileset and Junction
- 4.2.3.7. Migration and Purge Policy Overrides
- 4.2.3.8. Storage Class Threshold Overrides
- 4.2.4. Modifying a Storage Subsystem
- 4.2.5. Deleting a Storage Subsystem
- Chapter 5. HPSS Servers
- 5.1. Server List
- 5.1. Server Configuration
- 5.1.1. Common Server Configuration
- 5.1.1. Core Server Specific Configuration
- 5.1.2. Gatekeeper Specific Configuration
- 5.1.3. Location Server Additional Configuration
- 5.1.4. Log Client Specific Configuration
- 5.1.1. Log Daemon Specific Configuration
- 5.1.2. Migration/Purge Server (MPS) Specific Configuration
- 5.1.3. Mover Specific Configuration
- 5.1.3.1. Mover Specific Configuration Window
- 5.1.3.1. Additional Mover Configuration
- 5.1.3.1.1. /etc/services, /etc/inetd.conf, and /etc/xinetd.d
- 5.1.3.1.2. The Mover Encryption Key Files
- 5.1.3.1.3. /var/hpss/etc Files Required for Remote Mover
- 5.1.3.1.1. System Configuration Parameters on IRIX, Solaris, and Linux
- 5.1.3.1.1. Setting Up Remote Movers with mkhpss
- 5.1.3.1.2. Mover Configuration to Support Local File Transfer
- 5.1.1. Physical Volume Repository (PVR) Specific Configuration
- 5.1.1. Deleting a Server Configuration
- 5.1. Monitoring Server Information
- 5.1.1. Basic Server Information
- 5.1.1. Specific Server Information
- 5.1.1.1. Core Server Information Window
- 5.1.1.1. Gatekeeper Information Window
- 5.1.1.1. Location Server Information Window
- 5.1.1.2. Migration/Purge Server Information Window
- 5.1.1.3. Mover Information Window
- 5.1.1.1. Physical Volume Library (PVL) Information Window
- 5.1.1.2. Physical Volume Repository (PVR) Information Windows
- 5.1. Real-Time Monitoring (RTM)
- 5.2. Starting HPSS
- 5.1. Stopping HPSS
- 5.2. Server Repair and Reinitialization
- 5.1. Forcing an SSM Connection
- Chapter 6. Storage Configuration
- 6.1. Storage Classes
- 6.2. Storage Hierarchies
- 6.3. Classes of Service
- 6.4. Migration Policies
- 6.5. Purge Policies
- 6.6. File Families
- Chapter 7. Device and Drive Management
- Chapter 8. Volume and Storage Management
- 8.1. Adding Storage Space
- 8.2. Removing Storage Space
- 8.3. Monitoring Storage Space
- 8.4. Dealing with a Space Shortage
- 8.5. Volume Management
- 8.6. Monitoring and Managing Volume Mounts
- 8.7. New Storage Technology Insertion
- Chapter 9. Logging and Status
- Chapter 10. Filesets and Junctions
- Chapter 11. Files, Directories and Objects by SOID
- Chapter 12. Tape Aggregation
- Chapter 13. User Accounts and Accounting
- Chapter 14. User Interfaces
- Chapter 15. Backup and Recovery
- Chapter 16. Management Tools

device. Without the reservation, it is possible for other hosts to interleave SCSI commands to the
drive with those issued by HPSS. This effect could potentially lead to corruption of data.
Table 2. Recommended Settings for Tape Devices
Device Driver Mover Executable NO-DELAY
Support
Locate Support Write TM(0) to
Sync
IBM SCSI Tape hpss_mvr_ssd ON ON OFF
IRIX Native hpss_mvr_tcp ON ON OFF
Ampex hpss_mvr_dd2 OFF ON ON
AIX Native hpss_mvr_tcp ON OFF OFF
Linux Native hpss_mvr_tcp ON ON OFF
PVR (tape only). The name of the PVR that handles the removable media operations for the drive.
Drive Address. For tape drives, this is the name/address by which the PVR can access the drive. This
field isn't used by the PVL or PVR for disk drives; the administrator may use this as a comment. Many
sites duplicate the Device Name which makes it valuable as a query of drive information since it will
return the device information for the disk case (e.g. lshpss -drv).
Advice - For StorageTek robots: Drive Address configuration entries correspond to the
ACS,Unit,Panel,Drive Number used by ACSLS to identify drives. For example, the first drive in a typical
configuration has Drive Address 0,0,10,0.
For IBM 3584 LTO robots: The Drive Address configuration entries correspond to the SCSI address
(location) of the drive in the library. Determine the drive location by running an inventory on the library
either through the tapeutil utility supplied with the Atape driver or using the library console. Typically
the first drive is located at location 257 for a single frame library.
For IBM 3494 robots: The Drive Address configuration entries correspond to the hexadecimal Library
device number of the drive. Determine the Library device number by running the command
“/opt/hpss/bin/GetESANumbers /dev/rmtX” for each tape drive in the robot.
For SCSI PVRs: The Drive Address configuration entries correspond to the SCSI address (location) of
the drive in the library. Determine the drive location by running an inventory on the library either
through the device_scan utility or using the library console. Typically the first drive is located at
location 256 for a single frame library.
For operator mounted drives: For manually mounted drives, the drive address string is displayed to
operators when an explicit drive is selected for mounting. The drive address should therefore be a string
that easily communicates to an operator the drive in question (i.e., a name matching the label on the
exterior of the drive).
For AML robots: Leave the Drive Address field blank.
The AML PVR is supported by special bid only.
Controller ID. An indication of the adapter/bus that is in the data path to the device.
Advice - This field is used to attempt to mount individual volumes of a set of striped media on individual
controllers, when possible, to prevent contention on the data path. It is recommended that the drives that
are on the same adapter/bus have the same Controller ID. For drives in 3494 robots, the Controller ID
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 201