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

Clear List. Clears the list of mount requests. Note that this does not cancel any mount requests, but just
removes them from the list. Pending mounts will reappear in the window as the PVR periodically retries
the mounts. This can be useful for removing stale mount requests that, for some reason, never issued a
completion message to SSM. When this button is clicked from any SSM session, the Tape Mount
Requests windows on all SSM sessions will be cleared.
8.6.6. Administrative Tape Dismounts
HPSS provides the ability to administratively command a tape dismount in unusual situations, such as
when an administrator wants a tape dismounted without waiting for HPSS to do so, or when HPSS is
unable to do so due to a failure.
Administrative dismounts should only occur in exceptional error circumstances. Dismounting a tape may
cause the operations being performed on that tape to fail. A library dismount operation is unlikely to
occur while a mover has the device reserved for I/O.
Use the Devices and Drives list window to issue a dismount for the desired device/drive entry. A
confirmation window will pop up requiring you to confirm the dismount request.
8.7. New Storage Technology Insertion
As more advanced storage technology becomes available, there may be a need to replace used storage
media with newer volumes. HPSS provides a procedure for making this change. The procedure retires the
old volumes, introduces new volumes, moves the storage segments from the old to the new, and then
removes the old volumes.
The volume retirement feature is provided to facilitate new technology insertion. HPSS will not select a
retired volume to receive a new storage segment. In every other way, retired volumes behave normally.
Storage segments on retired disk volumes can be read and written normally. Storage segments on retired
tape volumes can be read normally. Attrition of segments through the usual processes of file deletion and
migration will cause retired volumes to gradually become empty.
A retired volume has the characteristic that its VV Condition is something other than RWC, and cannot
be changed to RWC. New storage segments can be created on a volume only when the VV Condition is
RWC, so new segments are not created in retired volumes.
To replace old technology volumes with new, the following outline serves as a guide, but the
administrator should be aware that the procedure will probably need to be tailored to the specific
circumstances of the change. This procedure applies to both tape and disk volumes:
1. Change the storage class definition by deleting and then recreating it using the same storage class
ID. The new storage characteristics must reflect the characteristics of the new storage technology
volumes. In addition, they should be compatible with other storage levels in the hierarchy.
Changes made to the storage class definition do not affect volumes that exist when the changes
are made. The characteristics of established volumes stay the same throughout their lifetimes.
Changes made to the storage class only affect the characteristics of volumes created after the
change is made.
2. Stop and restart the Core Servers and Migration Purge Servers that use the modified storage class.
These servers cache storage class definitions in memory and should have the opportunity to
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 291