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
5.1.2. RTM Detail
The RTM Detail window displays a snapshot of the details of the selected RTM requests from the RTM
Summary List window. This may contain information from multiple servers, Gatekeeper, Core and
Mover. The actual data displayed will be different for each server type and is displayed in a tree
structure. Each node of the tree can be expanded/collapsed by clicking the mouse on the tree node
indicator. A new snapshot can be taken and added to the display by pressing the Snapshot button. The
tree can be cleared by pressing the Clear button.
Each detailed snapshot taken for an RTM request will contain the date and time the snapshot was taken at
the top of the tree. Below the date and time there will be an rtm_req_detail_entry_t.
The fields contained in the rtm_req_detail_entry_t structure are;
ReqId. The RTM request identifier.
UserName. The printable username associated with this request (if available).
PathName. The HPSS pathname of the file associated with this request (if available).
Oldest_StartTimeDelta. Of all the RTM request records with this ReqId, this field holds the
age of the oldest when the snapshot was taken.
Newest_UpdateTimeDelta. Of all the RTM requests records with this ReqId, this field holds
the age of the request most recently updated by its server when the snapshot was taken.
Oldest_ServerName. The server holding the RTM request with the oldest age or
Oldest_StartTimeDelta.
Newest_ServerName. The server holding the RTM request with the most recent update age or
Newest_UpdateTimeDelta.
Each server type that generates RTM request records (Gatekeeper, Core and Mover) has a server specific
RTM data structure which will be displayed as a tree node below the rtm_req_detail_entry_t node.
These structures are only displayed if there is a server of that type involved in the RTM request. There
will be multiple entries if there are more than one server involved in the RTM request.
The server specific RTM records are called;
rtm_gk_detail_entry_t (Gatekeeper)
rtm_core_detail_entry_t (Core)
rtm_mvr_detail_entry_t (Mover)
The server specific data structures each have a Common and ReqInfo structure embedded in them. The
Common structure will contain the same fields for each server type.
The Common fields are;
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 146