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
port hpssgui and hpssadm clients must access to reach the System Manager.
This task can be made a bit easier if the System Manager RPC program number is labeled in the
portmapper. To do this, add a line for the System Manager in the /etc/rpc file specifying the program
number and a convenient rpc service name such as “hpss_ssm” (note that names may not contain
embedded spaces). Then this service name will show up in the rpcinfo output.
The format of the /etc/rpc file differs slightly across platforms. See the platform specific man pages for
the rpc file for details. The rpcinfo utility is typically found in either /usr/bin (AIX) or /usr/sbin (Linux).
3.2. Quick Startup of hpssgui
We recommend that hpssgui sessions be invoked from the user's desktop computer instead of on the
HPSS server machine. hpssgui is an application designed to run in the Java environment on the user's
desktop computer and to communicate with the remote SSM System Manager. If hpssgui is executed on
the remote System Manager host, it must run through an X windows session and it may run very slowly
in that environment. This is a limitation of Java and networks.
We recognize the value of using the remote X functionality as a quick way to get SSM running, but once
your system is up, it is highly recommended that you configure local desktop SSM hpssgui clients for all
HPSS administrators and operators. Local desktop hpssgui configuration is detailed in Section 3.3:
Configuration and Startup of hpssgui and hpssadm below.
Following are steps for quickly configuring and starting an SSM GUI client:
1. Use the hpssuser utility to create an SSM user with admin authority. See Section 3.3.2.1: The
hpssuser Utility on page 35 and the hpssuser man page for more information.
2. On Linux systems, set the JAVA_BIN environment variable to point to the Java runtime binary
directory. Set the variable in the environment override file, usually /var/hpss/etc/env.conf. It is
usually set to something like /usr/java5/bin. The default setting of $JAVA_BIN is /usr/java5/bin
which is the usual location of the java binary directory.
3. The mkhpss utility generates the ssm.conf SSM configuration text file when configuring the SM.
See the HPSS Installation Guide, Section 5.3: Install HPSS/DB2 and Configure HPSS
Infrastructure for more details. Verify the existence of the $HPSS_PATH_SSM/ssm.conf file.
4. Start the hpssgui script:
% /opt/hpss/bin/hpssgui.pl
· Note that the -m option can be used to specify the desired SSM configuration file to be used.
When this option is not specified, hpssgui.pl looks for the ssm.conf configuration file in the
current directory, then in the directory defined by the HPSS_PATH_SSM environment
variable (usually /var/hpss/ssm). If the script doesn't find a configuration file in either
directory, it will use default values to start the client.
· Note that the -d (debug) and -S (log file name) options can be used to capture all levels of
hpssgui logging in a text file. Bear in mind, however, that this can generate significant
amounts of log data. (See the hpssgui man page.)
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 33