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
• UTIME. Core Server bitfile time modified events.
• ACL_SET. Core Server access control list modification events.
• CHBFID. Core Server change bitfile identifier events.
• BFSETATTRS. Core Server set bitfile attribute events.
5.1.1.1. Log Policy
The server Log Policy may also be accessed from the Logging Policies window.
It is not necessary to define a log policy for every server. If no server-specific log policy is defined for
the server, the server will use the System Default Logging policy. In this case, the Log Policy tab on the
Server Configuration window will display the values from the System Default Logging Policy.
Note that in order for modifications to the log policy to take effect, the appropriate server must be
reinitialized. In most cases, the server which must be reinitialized is the Log Client which executes on
the same host as the server whose log policy was changed. The only exception is for Movers; when the
log policy of a Mover is modified, that Mover itself must be reinitialized in order for the log policy
changes to take effect.
See Section 9.2: Log Policies on page 295 for a description of the Logging Policies window, for detailed
definitions of each log message type, and for information on the System Default Logging Policy.
The Log Policy section of the Server Configuration window is common to all servers. In the example
window above, the server displayed is a Core Server.
Field Descriptions
Record Types to Log. These log message types will be sent to the log subsystem by this server.
• ALARM. If selected, Alarm messages generated by the server are sent to the log. It is strongly
recommended that this always be ON.
• EVENT. If selected, Event messages generated by the server are sent to the log. It is
recommended that this always be ON.
• REQUEST. If selected, Request messages generated by the server are sent to the log. Request
messages can easily flood the log on a busy system, so in many cases, this log type should be OFF.
• SECURITY. If selected, Security messages generated by the server are sent to the log. Security
log messages are usually relatively few in number, so this log type should be ON.
• ACCOUNTING. If selected, Accounting messages generated by the server are sent to the log.
• DEBUG. If selected, Debug messages generated by the server are sent to the log. It is
recommended that this be ON, particularly in the Core Server and Mover. Debug messages are
only generated when an error occurs and they can be very helpful in determining the cause of the
error.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 95