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
only if the Support Shelf Tape checkbox is selected. The alarm value must be 2 or greater.
Dismount Delay. When Defer Dismounts is checked, this value is used by the PVL to determine the
number of minutes that dismounts are delayed after the last data access.
Retry Mount Time Limit. The default value for this field is -1. When the default value (-1) is used, if an
error is encountered during a PVR mount operation, the mount will pend and be retried every 5 minutes.
Setting a value in this field will change the mount behavior to periodically retry the mount until the
specified time limit is exceeded. Once exceeded, an error is generated and the mount request is canceled.
If the mount request would have resulted in a write operation, the error returned will cause the Core
Server to set the VV Condition of the associated tape volume to DOWN. Once in DOWN state, the
volume will no longer be available for read or write operations. For further information about the Core
Server VV Condition, see Section 4.5.4.2: Core Server Tape Volume Information Window on page 471.
Drive Error Limit. This field is intended to be used in conjunction with the PVR Server Retry Mount
Time Limit. If the number of consecutive mount errors which occur to any drive in this PVR equal or
exceed this value, the drive is automatically locked by the PVL. The only mount errors that apply are
those set through the Retry Mount Time Limit mechanism. The Drive Error Count field in the PVL
Drive Information records the number of consecutive errors on a drive by drive basis. To turn off the
automatic drive disable feature, set the Drive Error Limit to 0 or -1. Since this field is employed by the
PVL, changing its value will not change drive disable behavior until the PVL is recycled.
Characteristics. Flags for the PVR:ismounts. If ON, the PVL will delay the dismounting of a tape
cartridge until the drive is required by another job or until the Dismount Delay time limit is exceeded.
• Support Shelf Tape. If ON, the PVR and the PVL will support the removal of cartridges
from the tape library using the shelf_tape utility.
Command Device. The name of the device that the PVR can use to send commands to the robot. For
AIX systems, this is generally /dev/lmcp0. For Linux systems, use the symbolic library name defined in
/etc/ibmatl.conf. The environment variable HPSS_3494_COMMAND_DEVICE will override the
value entered in this field. Only use the environment variable when using only one 3494.
Async Device. The name of the device that the PVR can use to receive replies from the 3494 robot. For
AIX systems, this is generally /dev/lmcp1. For Linux systems, use the symbolic library name defined in
/etc/ibmatl.conf. For TTY and LAN-attached robots, the Async Device may be the same as the
Command Device. The environment variable HPSS_3494_ASYNC _DEVICE will override the value
entered in this field. Only use the environment variable when using only one 3494.
5.1.1.1.1. 3494 PVR Additional Information
Configuration Requirements
When configuring an HPSS PVR to manage an IBM robot, the Drive Address configuration entries
correspond to the device number of the drive. Determine the device number by running the HPSS tool
GetESANumbers for each tape drive in the robot.
The HPSS PVR requires one or two LMCP device special files to access the robot. For AIX systems,
these files are usually named /dev/lmcpX and can be created using the System Management Interface
Tool (SMIT). The files can be defined to be either a Command Port or an Asynchronous (Async) Port.
The HPSS PVR requires both. By default, the PVR will expect the Command and Async ports to be
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 112