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
• Disabled - The device is locked, which makes it unavailable for use by HPSS.
• Unknown - The state of the device is not known to SSM; this is usually caused by the controlling
Mover being down or disconnected from SSM.
Device Admin State. The current administrative state of the device, as reported by its controlling Mover.
The possible states are:
• Locked - The device is locked and unavailable for use by HPSS.
• Unlocked - The device is unlocked and available for use by HPSS.
• Unknown - The state of the device is not known to SSM; this is usually caused by the controlling
Mover being down or disconnected from SSM
Mover. The descriptive name of the Mover that controls the device.
Mover Host. The host name of the Mover node (the node where the Mover runs).
Drive Address. The name used by the PVL/PVR to access the drive.
Drive Flag. This field describes possible actions that the PVL needs to perform for the drive. Possible
flags are:
• Clear - Nothing needs to be done.
• Modified - Set by SSM when the drive has been modified. It was added for a future feature;
currently unsupported.
• PVR/Mover Notify Pending - The PVL needs to notify the associated PVR and Mover that the
drive has been created or deleted.
• PVR Notify Pending - The PVL needs to notify the associated PVR that the drive has been
created or deleted.
• Mover Notify Pending - The PVL needs to notify the associated Mover that the drive has been
created or deleted.
• Abort PVR/Mover Notify – The PVL is aborting a pending notification.
Drive State. The current operational state of the drive, as reported by the PVL. The possible states are:
• Enabled - The drive is working normally.
• Disabled - The drive is not available for use by HPSS. This can occur if the drive is locked by an
SSM user, or if an error occurred when mounting or dismounting a cartridge on the drive.
• Broken - The PVL itself has detected a fatal error, and is shutting itself down.
• Unknown - The state of the device is not known to SSM; this is usually caused by the PVL being
down or disconnected from SSM.
Drive Admin State. The current administrative state of the drive, as reported by the PVL. The possible
states are:
• Locked - The drive is locked and unavailable for use by HPSS.
• Unlocked - The drive is unlocked and available for use by HPSS.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 204