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
GroupId. The Group ID of the user associated with this request.
HostAddr. The address of the originating host
RequestType. The type of this request (Open, Create or Stage).
Oflag. The Open flags associated with this file open request.
StageFlags. Flags associated with this file stage operation.
StageLength. The number of bytes to stage.
StageOffset. The offset of the file where the stage is to begin.
StageStorageLevel. The Storage Class level that the file will be staged to.
UserId. The ID of the user associated with this request.
WaitTime. The length of time this request has been waiting.
5.2. Starting HPSS
This section describes how to start and stop HPSS servers and prerequisite software.
5.2.1. Starting HPSS Prerequisite Software
Invoke the /opt/hpss/bin/rc.hpss script as root to start the HPSS prerequisite software such as DB2,
Kerberos and LDAP. By default, stdout and stderr from commands started by rc.hpss are not
manipulated. Specifying the "-o" option to rc.hpss will cause stdout and stderr of commands invoked
within the script to be sent to /dev/console, the terminal window where rc.hpss is running. When using
the "-o" option, one should ensure that the HPSSLOG environment variable is not set to "stdout" in the
env.conf file since this is likely to severely degrade HPSS' performance.
To start the prerequisite software, use the “-p” option to rc.hpss:
% su -
% /opt/hpss/bin/rc.hpss -p [start]
5.2.2. Starting HPSS Servers
Most HPSS servers are started via SSM which calls an appropriate Startup Daemon to begin execution of
the selected HPSS server. This means that SSM and the Startup Daemons must be started in a different
way. This section covers how to start the Startup Daemons, how to start SSM, and how to start the other
HPSS servers once SSM and the Startup Daemons are up and running.
5.2.2.1. Starting the Startup Daemons
Invoke the /opt/hpss/bin/rc.hpss script as root to start the HPSS Startup Daemon. By default, both stdout
and stderr are not redirected to /dev/console since this can have a negative impact on performance.
Specifying the “-o” option will cause this redirection of output.
If server output is to be redirected to /dev/console, ensure that the HPSSLOG variable in the env.conf file
is not set to stdout since this combination may severely degrade the HPSS performance.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 149