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
ReqId. The RTM request identifier.
ReqCode. The action or operation that this request is currently executing. Examples include
"Mover write", "PVL verify", "write tm" (tape mark), etc.
ReqState. The state of the requested operation. Examples include "in progress", "suspended",
"blocked", etc.
ServerDescName. The descriptive name of the server that holds this RTM request record.
StartTimeDelta. The age of this request since it entered the server. That is, the time difference
between when the request entered and when this snapshot was taken.
UpdateTimeDelta. The time difference between when this server last updated this RTM record
and when this snapshot was taken.
ThreadId. The ID of the thread processing this request, useful in attaching to the thread to
examine its state in the case of a hung request.
ProcessId. The ID of the UNIX process that is processing this request, useful in attaching to the
process to examine its state in the case of a hung request.
WaitString. A text string indicating what the request is currently waiting for inside this server.
The ReqInfo portions of the server specific data structures will contain different fields depending on the
server type. Not all fields for a particular server specific ReqInfo structure will be displayed. Only those
fields that have valid data in them for the particular state of the RTM request will be displayed. The
possible fields for each server specific ReqInfo are listed below.
The Core server ReqInfo structure may contain any or none of the following fields;
SubsystemId. The ID of the HPSS subsystem owning this request.
UserRealmId. The Realm ID of the user associated with this request.
FilesetId. The ID of the fileset of the file associated with this request.
FilesetName. The text string name of the fileset of the file associated with this request.
BfId. The Bitfile ID of the file associated with this request.
BfPathname. The HPSS pathname of the file associated with this request.
UserId. The ID of the user associated with this request.
UserGId. The Group ID of the user associated with this request.
COSId. The Class Of Service ID of the file associated with this request.
BFS_SClassId. The Storage Class ID known to the bitfile server of the file segment associated
with this request.
BFS_BytesRequested. The number of bytes to be moved in this request as known by the bitfile
server.
BFS_BytesMoved. The number of bytes already moved for this request as known by the bitfile
server.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 147