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
4.2.3.7. Migration and Purge Policy Overrides
The migration and purge policies contain two elements, the basic policy and the storage subsystem
specific policies. This can be seen on the Migration Policy and Purge Policy windows. If a given
migration or purge policy does not contain any subsystem specific policies, then the basic policy applies
across all storage subsystems and no other configuration is needed. If it is desired for migration or purge
to behave differently than specified in the basic policy in a given storage subsystem, then a storage
subsystem specific policy should be created for that subsystem. A subsystem specific policy allows some
or all of the values in the basic policy to be overridden for the given storage subsystem. See Section
6.4.2: Migration Policy Configuration on page 182 and Section 6.5.2: Purge Policy Configuration on
page 190 for more information.
4.2.3.8. Storage Class Threshold Overrides
The warning and critical thresholds given on the Storage Class Configuration window apply across all
storage subsystems unless specified otherwise. The Subsystem Thresholds button on the Configured
Storage Class list window allows the default thresholds to be overridden for specified storage
subsystems. See Section 6.1.1: Configured Storage Classes Window on page 157 for more information.
4.2.4. Modifying a Storage Subsystem
If modifications are made to an existing Storage Subsystem configuration, the Core Server and the
Migration Purge Server for the subsystem must be recycled.
4.2.5. Deleting a Storage Subsystem
Always contact HPSS customer support before deleting a subsystem definition. An improperly
deleted subsystem can cause serious problems for an HPSS system.
It is critical that no files or directories exist within a storage subsystem before it is deleted. It is
important to verify that all of the DB2 metadata tables associated with the storage subsystem
being deleted are empty.
To verify that all files have been removed from the subsystem, perform the following steps:
1. Run the dump_acct_sum utility on the subsystem. Be sure to specify the subsystem ID with the
-s option as this utility defaults to subsystem 1. The output from the utility should indicate that 0
files exist in the subsystem.
2. As a second verification do the following:
A. Run the db2 command line utility program.
B. Connect to the subsystem database (e.g., connect to subsys1).
C. Set the schema (e.g., set schema hpss).
D. Issue the following SQL command:
db2> select count(*) from bitfile
The result of the command should indicate 0 rows in this table.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 81