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
To start the Startup Daemon, use the “-d” option to rc.hpss:
% su -
% /opt/hpss/bin/rc.hpss -d [start]
5.2.2.2. Starting SSM
The SSM System Manager configuration metadata should have already been created by mkhpss as part
of the the infrastructure configuration. After SSM is started, this configuration metadata may be modified
if necessary. Refer to the HPSS Installation Guide, Section 2.3.4: HPSS Infrastructure for more
information.
The SSM server startup script, rc.hpss, can be used to invoke the HPSS System Manager. The server
requires a number of environment variable values to be used as its command line arguments and to be
used to configure and manage the HPSS servers. These variables are defined by the system. The system
defined values can be overridden in the env.conf file. They should have been edited to reflect the site’s
configuration during the HPSS infrastructure configuration phase.
Before starting up the System Manager, ensure that DB2 and other prerequisite software are up and
running.
The rc.hpss script will not start the System Manager if it is already running on the same node. Ensure that
only one instance of the SSM System Manager is running at any one time.
To start the SSM System Manager, use the “-m” option to rc.hpss:
% su -
% /opt/hpss/bin/rc.hpss -m [start]
To start an SSM graphical user interface or command line interface session, see Section 3.3:
Configuration and Startup of hpssgui and hpssadm on page 34, or the hpssgui or hpssadm man page. For
best performance, it is recommended that the SSM graphical user interface (GUI) be installed on the
SSM user's desktop machine. However, authorized SSM users can invoke the hpssgui script directly from
the HPSS server machine if desired. However, most users of the SSM command line interface (hpssadm)
will most likely invoke the script on the server machine.
5.2.2.3. Starting Other HPSS Servers
Other servers are started using SSM or can be automatically started upon startup of the System Manager
by using the Core Server Auto Startup feature. This feature can be set using the Core Server
Configuration window. Refer to Section 5.1.1.1: Execution Controls on page 90.
When starting a server from SSM using the Servers window, one or more HPSS servers can be started by
the same request. SSM forwards the server’s configuration data to the appropriate HPSS Startup
Daemon. The Startup Daemon invokes the server with the appropriate input arguments. After the server
is started, SSM attempts to establish a connection with the server. The server status is reported in the
Status field on the Servers window. Refer to Section 5.1: Server List on page 83 for more information.
Before starting a server, ensure that DB2 and other prerequisite software are running, Kerberos is
running (if using Kerberos authentication), that the Startup Daemon on the server’s node is running and
has a connection with SSM, and that the server is configured and its Executable flag is set. Ensure that
any required PVR controllers are up and running before bringing up the PVRs.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 150