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
administrator.
Start Time. The date and time when the most recent migration run started. It may still be
running.
End Time. The date and time when the last migration run completed.
Total Units Processed. The amount of space in the storage class which has been migrated during
the current or or most recent migration run. For tape storage classes running the tape volume
migration algorithm, this is a number of virtual volumes (VVs).
Control. This pull-down can be used to send commands to the MPS regarding migration on this
storage class. Click on it to drop down a list of control options. These are:
• None - Nothing has been selected for the migration Control.
• Start - If the migration state is Waiting, this starts the migration and puts it into the
Running state.
• Stop - If the migration state is Running, this stops the migration and puts it into the
Waiting state.
• Suspend - If the migration state is Waiting or Running, this puts the migration into the
Suspended state.
• Resume - If the migration state is Suspended, this returns it to Waiting and allows MPS
to again begin scheduling migration runs.
• Reread policy - Tells the MPS to refresh its migration policy information by rereading
the policy.
Pending Operations. When the MPS cannot respond immediately to a Control command, a
command may be saved as pending. Any such pending operations are displayed here.
8.4. Dealing with a Space Shortage
If free space warning thresholds are exceeded in a storage class, HPSS will warn the administrator with
messages in the Alarms and Events window. Before the available storage space in a storage class drops to
a level where the storage class may no longer be able to satisfy requests, efforts should be made to create
additional free space. This can be accomplished by three methods.
The first method is to use the migration and purge functions to free up space. Migration and purge can be
forced manually to run; see Section 8.4.1 Forcing Migration and Section 8.4.2 Forcing Purge. For a long
term solution, it may be desirable to tune the migration and purge policies to cause the automatic
migration and purge operations to occur more frequently. This method of increasing storage space works
for all levels in the Class of Service hierarchy except the lowest level.
The second method is to add additional storage volumes to the storage class using the normal import and
create resources procedures. See Section 8.1 Adding Storage Space on page 223.
The third method is to increase free tape storage space by repacking sparse volumes and reclaiming
empty volumes. The repack program moves information from sparsely filled volumes to other volumes
in the same storage class. When the repack is finished, a number of volumes will be cleared of data. To
make these volumes ready for reuse, they must be processed by the reclaim program, which refreshes the
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 258