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
Chapter 9. Logging and Status
9.1. Logging Overview
The purpose of logging is to record events of interest that occur in HPSS in the sequence they occur to
support diagnostic research.
HPSS provides eight log message types:
• Alarm
• Event
• Status
• Debug
• Request
• Security
• Accounting
• Trace
The purpose of each of these log message types is described later in this chapter.
Log messages are deposited in four places. Certain high priority messages are transmitted to SSM and
displayed on the Alarms and Events window. This allows the administrator to see events unfolding in
close to real time. All log messages are coded in a binary format and written to one of two central log
files. The Log Daemon writes these files alternatively. Also, the Log Client on each host writes a large
circular ASCII file with log messages just for that host as they are received. This file makes it easy for
the administrator to copy the file and quickly search it for an event of interest using ordinary text
processing tools. Finally, if HPSSLOGGER is set, HPSS will log to the location specified by HPSS
LOGGER (syslog or stdout) if the logger isn't running/available.
The HPSS logging facility is comprised of two types of servers, Log Clients and the Log Daemon. Log
Clients run on each HPSS node. A Log Client receives log messages from each HPSS server running on
its node and filters those messages based on the configured log policies. Messages that pass the filter are
logged locally based on the Log Client’s configuration and are then sent to the Log Daemon. The Log
Daemon checks the log policies to see which messages are to be displayed in the Alarms and Events SSM
window before entering them into the central log.
For useful logging to take place, it is important that the log policies, Log Clients and Log Daemon are all
configured and managed properly.
The HPSS logging system includes these components:
1. Log Policies (Section 9.2: Log Policies on page 295)
2. Local logs (Section 9.5 Error: Reference source not found on page 301)
3. The Central Log (Section 9.3: Managing the Central Log on page 299)
4. Log Clients and Log Daemon (Section 5.1.4: Log Client Specific Configuration on page 100 and
Section 5.1.1: Log Daemon Specific Configuration on page 101)
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 294