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
COS Change Retry Limit, Tape Dismount Delay, Tape Handoff Delay, PVL Max Connection Wait,
Fragment Trim Limit and Fragment Smallest Block can be changed in the Core Server while the
server is running by changing the value on this screen, updating the metadata, then re-initializing the
appropriate Core Server. The Core Server re-reads the metadata and changes its internal settings. The
changes take effect the next time the settings are used by the server. See Section 5.2.2: Reinitializing a
Server on page 154 for more information.
Changes made to the rest of the settings on this screen take effect the next time the server is started.
Field Descriptions
Root Fileset Name. Core Servers can create and support multiple filesets, but an initial fileset is
required for each Core Server. The Root Fileset Name designates which of these filesets will be used by
the Core Server to resolve the pathname “/” in the subsystem. Other filesets served by this Core Server,
or from other Core Servers in the HPSS system may be joined to this fileset by junctions.
Root Fileset ID. The Fileset ID of the fileset named in Root Fileset Name.
Maximum Open Bitfiles. The maximum number of bitfiles that can be open simultaneously.
Maximum Active I/O Requests. The maximum number of simultaneous I/O requests allowed.
Maximum Active Copy Requests. The maximum number of simultaneous copy requests allowed.
COS Change Retry Limit. This is the maximum number of attempts that will be made to change the
class of service of a file. If set to 0, COS change will continue to be attempted until it is successful. If a
positive value is provided, the COS change request will be dropped after it has failed the configured
number of times.
Tape Dismount Delay (seconds). The amount of time, in seconds, a mounted tape volume will remain
idle before being dismounted by the Core Server. Larger values may reduce undesirable tape
dismount/remount events, at the expense of lower tape drive utilization.
Tape Handoff Delay (seconds). The amount of time, in seconds, a mounted tape will be held in a
client's session before become eligible to be handed off to another client that wishes to use the tape.
PVL Max Connection Wait (seconds). The amount of time, in seconds, the Core Server will wait to
connect to the PVL before declaring an error in pending PVL jobs.
Fragment Trim Limit (clusters). Fragment Trim Limit sets the lower limit of the number of clusters
that will be trimmed from a disk segment extent, when the extent turns out to be longer than the needed
length. Larger values tend to reduce disk fragmentation, but at the expense of increased slack space.
Fragment Smallest Block. Fragment Smallest Block sets the boundary used to determine where to
remove excess clusters from allocations that have excess space. The smallest block returned to the free
space map from the excess space at the end of an extent will be this size or larger.
COS Copy to disk. If ON, all copy operations associated with COS changes should be directed to disk
if the hierarchy has a disk storage class at its top level. If OFF, COS changes are not automatically
copied to the disk level. If there is a tape level in the hierarchy, they will go there instead.
5.1.1.1. Additional Core Server Configuration
Certain aspects of the operation of the Core Server can be controlled by setting environment variables.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 97