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
user does not specify a COS or any hints with the creation request. The global configuration specifies a
default COS for an entire HPSS installation. Selecting a COS on the storage subsystem configuration
window allows the global value to be overridden for a particular subsystem.
If the field is blank, the global default COS will be used. If no Classes of Service are configured, this
value can be updated after the Classes of Service are in place.
Subsystem Name. The descriptive name of the storage subsystem. This field may be set only when the
storage subsystem is created. The name should be unique and informative. It can contain a character
string up to 31 bytes long. The default value is “Subsystem #<ID>”.
Database Name. The name of the database to be used to store the metadata for the storage subsystem.
Gatekeeper. The default value is “None”.
Advice - If an appropriate Gatekeeper has not yet been configured, simply leave this configuration entry
blank. It can be updated after the Gatekeeper is in place.
Allowed COS list. A list of Classes of Service that can be used by this subsystem. To allow a COS to be
used by this subsystem, the corresponding checkbox must be selected in the Allow column of the list. At
least one COS must always be selected. The user will not be permitted to de-select the COS defined to
be the Default Class of Service. If this subsystem configuration does not have a Default Class of Service
defined, then the COS chosen as the Global Configuration’s Default Class of Service cannot be de-
selected.
Note that a newly created COS will not appear in the selection list until the Core Server and
Migration Purge Server associated with the subsystem have been recycled. When new Classes of
Service are added, the initial allowed state for that COS is determined by the current setting for
the other Classes of Service. If all previous Classes of Service were allowed, the new COS will
be allowed. Otherwise, the new COS will be disallowed.
Advice - By default, the servers in a subsystem are able to use any configured COS. This table allows an
administrator to prevent a subsystem from using particular Classes of Service.
When a new Class of Service is added to a system, it will automatically be enabled for all subsystems
which have no disabled Classes of Service. It will be disabled in all other subsystems. If this is not the
desired configuration, the COS will have to be allowed/disallowed for each subsystem individually.
Disallowing all Classes of Service in a subsystem is not permitted.
Metadata Space Warning Threshold. The Core Server in this subsystem will issue a warning alarm
periodically and set its Opstate to Major when the percentage of used space in any DB2 tablespace in this
subsystem’s database exceeds this value.
Metadata Space Critical Threshold. The Core Server in this subsystem will issue a critical alarm
periodically and set its Opstate to Critical when the percentage of used space in any DB2 tablespace in
this subsystem’s database exceeds this value.
Metadata Space Monitor Interval. The Core Server for this subsystem will check the metadata usage
statistics at the indicated interval, specified in seconds. If a value of 0 is specified, the Global
Configuration setting will be used for this storage subsystem. The minimum value for this field is 1800
seconds (30 minutes).
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 78