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

Table 3. Linux System Parameters
Parameter
Name
Minimum Value Parameter Description
SEMMSL 512 Maximum number of semaphores per ID
SHMMAX 0x2000000 Maximum shared memory segment size
(bytes)
5.1.3.1.1. Setting Up Remote Movers with mkhpss
The mkhpss utility may be used to copy the files needed for a remote Mover from the root
subsystem machine, to create the files which may not be copied, to install the required files on
the remote Mover machine, and to configure the inetd to run the remote Mover.
To create the necessary files, run mkhpss on the root subsystem machine. From the Root Subsystem
Machine menu, select the Create Config Bundle option. From this window, set the desired name of the
config file bundle and push the Create Config Bundle button.
To install the files and configure the inetd on the remote Mover machine, transfer the created config
bundle to the remote Mover machine and run mkhpss on the remote Mover machine. From the
Mover/Client Machine menu, select the Install Config Bundle item. On this window, set the approprate
name of the bundle file and push the Install Config Bundle button.
Next, select the Mover/Client Machine menu Configuration submenu, and from this, the Security
Services item. From this window, select the authentication mechanism (Kerberos or Unix) using the
drop down menu of the Authentication Mechanism field. For Kerberos, complete the remaining fields
on the window and push the Configure Security Services button to set up the required files. For Unix,
there is nothing further to configure on this window.
Next, still under the Mover/Client Machine menu Configuration submenu, select the Other Services
item. On this window, select the checkbox for “Configure any Movers for this machine”. This checkbox
instructs mkhpss to add the proper lines for the Movers to /etc/services. It also instructs it, depending
upon the operating system type, either to modify the /etc/inetd.conf file or to add the appropriate
configuration file to the /etc/xinetd.d directory to support the Movers. On this same window, select the
checkbox for “Set any system parameters necessary for HPSS”; this configures the local system settings
described in section 5.1.3.1.1: System Configuration Parameters on IRIX, Solaris, and Linux on page
106. At this time, there are no additional system parameters to set for AIX, so it is not actually necessary
to select this checkbox for AIX hosts.
5.1.3.1.2. Mover Configuration to Support Local File Transfer
The Mover local file transfer (LFT) protocol allows the Movers to transfer data directly between a UNIX
file system and HPSS.
Caveats:
• This transfer can only occur if both the Mover and the clients have direct access to the UNIX
filesystem on which the file resides.
• If the multinode features of the Parallel FTP Client are used, the UNIX filesystem must be global
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 108