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
will begin logging alarms indicating that the appropriate tape has yet to be checked-in. The frequency of
these alarms is controlled by the Shelf Tape Check-In Alarm field of the PVR-specific configuration
window.
The requests are displayed in chronological order. Each time such a request is received by SSM, it is
added to the list, but duplicate requests for the same tape are not displayed. When a message is received
indicating that the check-in request has been satisfied, the request is removed from the window. For
operator PVRs such check-in requests mean that a tape must be mounted by hand.
The maximum number of tape check-in messages that can be displayed on the Tape Check-In Requests
window is 100. When this limit is exceeded, some tape check-in notifications will be lost.
If the Auto Popup checkbox is selected, this window will automatically reopen whenever a new tape
check-in request is received. To open this window manually, select the Monitor menu on the Health and
Status window, from there select the Tape Requests submenu, and from there select the Check-In menu
item.
The HPSS shelf_tape utility may be used to move tapes from off-line storage to a tape library.
Field Descriptions
PVR. The descriptive name of the PVR that owns the cartridge.
Cart ID. The six-character label identifying the cartridge to be inserted into the robot.
Side. The side (partition) number to be mounted. This may be blank.
I/O Port. The descriptive name of the I/O port where the cartridge will be placed.
Update Time. The date and time when the check-in request was last updated.
Request Time. The date and time that the check-in request was first received by the SSM.
Elapsed Time. The length of time (days-hours:min:sec) that the check-in request has been waiting.
Buttons and Checkboxes
Auto Popup. If ON, this window will be opened automatically if it is not already on the screen when a
check-in request is received.
Clear List. Clears the list of check-in requests. Note that this does not cancel any check-in requests, but
just removes them from the list. Pending check-in requests will reappear in the window as the PVR
periodically retries the check-in of cartridges. This can be useful for removing stale check-in requests
that, for some reason, never issued a completion message to SSM. When this button is clicked from any
SSM session, the Tape Check-In Requests windows on all SSM sessions will be cleared.
8.6.5. Tape Mount Requests Window
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 289