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
• TRACE. If selected, Trace messages generated by the server are sent to the log. It is
recommended that this be OFF for all servers except the Mover. These messages give detailed
information about program flow and are generally of interest only to the server developer. In
normal operation, logging Trace messages can flood the log with very low level information. In
particular, it is important to avoid TRACE for the SSM System Manager Log Policy.
• STATUS. If selected, Status messages generated by the server are sent to the log.
Record Types for SSM. These log message types will be sent to the Alarms and Events window.
• SSM ALARM. If selected, Alarm messages generated by the server are sent to SSM. It is strongly
recommended that this always be ON.
• SSM EVENT. If selected, Event messages generated by the server are sent to SSM. It is
recommended that this always be ON.
• SSM STATUS. If selected, Status messages generated by the server are sent to SSM. It is
recommended that this always be ON.
Associated Button Descriptions
Use Default Log Policy. This button is used to configure the server to use the System Default Logging
Policy. The System Default Logging Policy is defined on the Global Configuration Window. Refer to
Section 4.1: Global Configuration Window on page 72.
If no server-specific log policy is defined for the server, the server uses the System Default Logging
Policy and this button is inactive. The values from the System Default Logging Policy are displayed in
this window.
To define a server-specific log policy, alter the fields in this window as desired and press the Add button.
A new log policy will be created for this server and the Use Default Log Policy button will become
active. The new log policy will also be added to the Logging Policies list window.
To remove the server-specific log policy, press the Use Default Log Policy button. The button will
become inactive again and the values of the System Default Logging Policy will be displayed in the
window. The server-specific log policy will be deleted from the system and from the Logging Policies
window.
To modify the server-specific log policy, alter the fields in this window as desired and press the Update
button.
5.1.1. Core Server Specific Configuration
A separate Core Server must be configured for each storage subsystem.
The Specific tab of the Core Server Configuration window allows you to view and update the type-
specific configuration for the Core Server.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 96