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
Storage Class Update Interval (seconds). The interval that indicates how often the MPS will query the
Core Server in its subsystem to get the latest storage class statistics. This is also the interval the MPS
uses to check whether it needs to initiate a purge operation on the storage class based on the associated
purge policy. The valid range for this field is 10-600.
Maximum Volumes for Whole File Migration. The maximum number of tape virtual volumes that will
be mounted for any tape storage class using the Migrate Volumes and Whole Files option. Migration of
other storage classes, end user stage requests, and many other factors should be considered when
deciding on this value.
Core Server API Failures Allowed. The maximum number of consecutive Core Server API failures
allowed before MPS aborts a migration or purge run. This applies to both disk and tape migration as well
as disk purge. If this limit is reached during a disk migration run, migration skips to the next hierarchy to
which that disk storage class belongs. Once the run has attempted to migrate all such hierarchies the run
will end. If this limit is reached during a disk purge or tape migration run, the migration or purge run
aborts.
MPS Report File Name (path/prefix). A prefix string used by the MPS to construct a migration report
file name. The full file name will consist of this string with a date string and subsystem ID appended to
it. If this field is left blank, no migration reports will be generated. If a usable path prefix is not specified,
the location of the migration report files may be unpredictable. A new MPS report file is started every 24
hours.
5.1.3. Mover Specific Configuration
5.1.3.1. Mover Specific Configuration Window
This tab of the Mover Configuration window allows you to update and view the type-specific
configuration for the Mover.
The server must be recycled in order for changes to become effective.
The Mover cannot be configured entirely from the SSM window. See Section 5.1.3.1: Additional Mover
Configuration on page 104, for further necessary configuration.
Field Descriptions
Encryption Key. An encryption key used to secure the Mover's interface with the Core Server. A
specific value may be entered in the field or a random value may be generated by clicking on the
Generate button. The default value is 0. A non-zero value must be configured to allow client access to
the Mover’s data interface. See Section 5.1.3.1: Additional Mover Configuration on page 104, for further
information about the encryption key.
Buffer Size. The buffer size used for double buffering during data transfers. The default buffer size is set
to 1,048,576 bytes (1 MB). This value should be tuned based on device and networking configuration
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 102