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
If a migration policy is added to a storage class after files are created in the storage class, those files
may never be migrated. Use the mkmprec utility to correct this problem. See the mkmprec man page for
more information.
Warning Threshold. A threshold for space used in this storage class expressed as a number of empty
tape volumes. Alarms will be sent to SSM periodically when the number of empty tapes in the storage
class falls below this value, and the Space Thresholds field on the HPSS Health and Status window will
be changed to Warning. Note that this field will not have any effect if overridden by Storage Subsystem-
Specific Thresholds.
Critical Threshold. Another threshold for space used in this storage class expressed as a number of
empty tape volumes. Alarms will be sent to SSM periodically when the number of empty tapes in the
storage class falls below this value, and the Space Thresholds field on the HPSS Health and Status
window will be changed to Critical. Note that this field will not have any effect if overridden by Storage
Subsystem-Specific Thresholds.
Optimum Access Size. The optimal transmission size to be used for a transfer request using this storage
class. (Not currently used by HPSS. May be used by site specific applications)
Average Latency. The average time (in seconds) that elapses when a data transfer request is scheduled
and the time the data transfer begins.
Maximum VVs to Write. The number of tape virtual volumes in the storage class that a Core Server
will use for concurrent writes.
Advice - Small values in this field restrict files being written in the storage class to a small number of
tapes, reducing the number of tape mounts. The number of tape drives used to write files in the storage
class will be limited to approximately the value of this field times the stripe width of the mounted VVs.
Read operations are not limited by this value.
Storage Segment Size
Media Type. The media type associated with the storage class.
Media Block Size (MBS). The Media Block Size is the size in bytes of a physical data block on the
media. For tape, this can be almost any value within reasonable limits. If the tape hardware has a
recommended physical block size, use that value.
Advice - The Media Block Size should be set to a value appropriate for the volume type. See the HPSS
Installation Guide, Section 3.10.1.1: Media Block Size Selection for some recommendations.
See also Device I/O Rate and Seconds Between Tape Marks in this section.
VV Block Size (VVBS). The virtual volume block size is the number of bytes written to an element of a
striped VV before the data stream moves to the next stripe element. It can be thought of as the stride
length of striped data transfer operations. The length of the VV block has an effect on the striping
efficiency. Short VV blocks cause more protocol overhead when writing striped devices. In non-striped
applications, VV Block Size has little meaning so any convenient multiple of the Media Block Size will
do.
Advice - When choosing a VV Block Size, the administrator should consider the characteristics of any
data source or sink the storage class that will be copied to or from. Best performance of striped copies
usually occurs when the VV Block Sizes of the source and sink are equal. This minimizes the data
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 164