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
Range End. If this field is zero, Port Range End field must also be zero.
Port Range End. Used in conjunction with Port Range Start (See above). Valid values are zero or any
TCP port number to which the Mover may bind (that is greater than or equal to the value of Port Range
Start). The default value is 0. If non-zero, this field must be equal or greater than Port Range Start. If
this field is zero, Port Range Start field must also be zero.
5.1.3.1. Additional Mover Configuration
The part of the Mover that handles accessing configuration metadata and servicing the Mover
administrative interface runs on the core server platform , while the part of the Mover (with which the
PVL and Core Servers communicate) that manages the storage devices and performs data transfers runs
on a remote node. To support this mode of operation, there is some additional configuration which must
be done on the remote node.
This additional configuration may be performed using mkhpss. See Section 5.1.3.1.1: Setting Up Remote
Movers with mkhpss on page 108.
Alternately, the configuration may be performed manually using the instructions from these sections:
• 5.1.3.1.1: /etc/services, /etc/inetd.conf, and /etc/xinetd.d on page 104.
• 5.1.3.1.2: The Mover Encryption Key Files on page 105.
• 5.1.3.1.3: /var/hpss/etc Files Required for Remote Mover on page 106.
• 5.1.3.1.1: System Configuration Parameters on IRIX, Solaris, and Linux on page 106.
5.1.3.1.1. /etc/services, /etc/inetd.conf, and /etc/xinetd.d
To invoke the remote part of the Mover, inetd on the remote node is utilized to start the parent process
when a connection is made to a port based on the Mover’s type specific configuration (see Section 5.1.3:
Mover Specific Configuration on page 102).
An entry must be added to the /etc/services file so that inetd will listen on the port to which the Mover
client process will connect. The port number is one greater than that configured for the “TCP Listen
Port” in the Mover’s type specific configuration. For example, if the configured listen port is 5001, the
following line must be added to /etc/services:
hpss_mvr1 5002/tcp
For non-Linux systems
An entry must be added to the /etc/inetd.conf file which defines which executable to run and the
arguments to use when a connection is detected. The entry must use the service name specified for the
Mover in /etc/services. The sole argument (other than the program name) is the pathname to a file that
contains an ASCII representation of the configured encryption key for the Mover (see the next section for
further details). For example, for the /etc/services entry added above, the corresponding /etc/inetd.conf
entry would be:
hpss_mvr1 stream tcp nowait root /opt/hpss/bin/hpss_mvr_tcp
hpss_mvr_tcp /var/hpss/etc/mvr_ek
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 104