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
must be greater than zero and is used if the Gatekeeping Site Interface returns a wait time of zero for the
create, open, or stage request being retried. Changing the value of this field will cause the Gatekeeper to
use the new value until the next restart at which point it will then go back to using the value defined in
the Gatekeeper Configuration window. Refer to Section 5.1.2 Gatekeeper Specific Configuration on
page 98.
Site Policy Pathname (UNIX). This field can only be set from the Gatekeeper Configuration window.
Refer to Section 5.1.2 Gatekeeper Specific Configuration on page 98.
Administrative Activity Statistics:
These fields are internal volatile statistics for the Gatekeeper. Each row describes a different API. There
are three columns: Calls, Errors and Retries. Each of these columns represent a count of the number of
calls, errors, and retries since the Statistics were (re)set. The Calls column is the number of times the
API was called. The Errors column is the number of times the API call resulted in an error being
returned. The Retries column is the number of times that the API call resulted in the HPSS_ERETRY
error being returned to the Client API. The Retries column only applies to API requests that may return
the HPSS_ERETRY status. A retry is not counted as an error.
The Statistics are (re)set to zero whenever the Gatekeeper is recycled or the Reset button is clicked.
• Get Basic Server Info. Statistics from the gk_admin_ServerGetAttrs API.
• Set Basic Server Info. Statistics from the gk_admin_ServerSetAttrs API. This API is called by the
SSM System Manager when the Gatekeeper's Basic Server Information window is opened.
• Get Gatekeeper Server Info. Statistics from the gk_admin_GKGetAttrs API.
• Set Gatekeeper Server Info. Statistics from the gk_admin_GKSetAttrs API. This API is called by
the SSM System Manager when the Gatekeeper Information window is opened.
• Creates. Statistics from the gk_Create API. This API is called by the Core Server when the
Gatekeeper is monitoring Create Requests.
• Auth Caller Creates. Statistics from authorized caller (e.g. MPS) calls to the gk_Create API.
• Creates Completed. Statistics from the gk_CreateComplete API. This API is called by the Core
Server when the Gatekeeper is monitoring Create Requests and the create completes.
• Opens. Statistics from the gk_Open API. This API is called by the Core Server when the
Gatekeeper is monitoring Open Requests.
• Auth Caller Opens. Statistics from authorized caller (e.g. MPS) calls to the gk_Open API.
• Closes. Statistics from the gk_Close API. This API is called by the Core Server when the
Gatekeeper is monitoring Open Requests and the file is closed.
• Stages. Statistics from the gk_Stage API. This API is called by the Core Server when the
Gatekeeper is monitoring Stage Requests.
• Auth Caller Stages. Statistics from authorized caller (e.g. MPS) calls to the gk_Stage API.
• Stages Completed. Statistics from the gk_StageComplete API. This API is called by the Core
Server when the Gatekeeper is monitoring Stage Requests and the stage completes.
• Client Clean Ups. Statistics from the gk_CleanUpClient API. This API is called by the Core
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 131