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
Field Descriptions
Server Name. A unique descriptive name given to the server. Ensure that the Server Name is unique. A
server’s descriptive name should be meaningful to local site administrators and operators, in contrast to
the server’s corresponding UUID, which has meaning for HPSS. For HPSS systems with multiple
subsystems it is very helpful to append the subsystem ID to the Server Name of subsystem-specific
servers. For instance, “Core Server 1” for the Core Server in subsystem 1.
Before modifying this field, check whether this server is using the default log policy or its own custom
log policy (see Section 5.1.1.1: Log Policy on page 95). If the server is using its own custom log policy,
modify it to use the default log policy. Skipping this step will cause an extraneous log policy to remain in
the system.
Server ID. A UUID that identifies a server to HPSS. A unique value is automatically generated and
displayed for new servers. While you are permitted to modify this field by hand, such a practice is not
recommended because of the danger that you could type in a UUID which is not unique within the entire
HPSS realm. This field may only be modified in Add mode.
Server Type. The type of the HPSS Server.
Server Subtype. The subtype of the selected server. This field is only used by the PVR servers to specify
the type of PVR (e.g. STK).
Storage Subsystem. Name of the HPSS Storage Subsystem to which this server is assigned. This field is
required for the Core Server and Migration/Purge Server. For all other servers this field is not displayed.
The following rules apply to this field:
• The Storage Subsystem Configuration must exist before configuring Core Servers or
Migration/Purge Servers.
• Core Servers and Migration/Purge Servers must have a valid storage subsystem set in this field
before SSM will allow the server configuration to be created.
• No more than one Core Server and one Migration/Purge Server can be assigned to any one
subsystem.
• This field can only be modified in Add mode.
5.1.1.1. Execution Controls
The Execution Controls section of the Server Configuration window is common to all servers. In the
example window above, the server displayed is a Core Server.
Field Descriptions
Execute Pathname. The UNIX file system path name to a server’s executable image file. This file must
reside on the node specified by Execute Hostname. Use the full UNIX path name; otherwise, the Startup
Daemon will try to start the file out of the current working directory of the Startup Daemon.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 90