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
movement protocol overhead and helps to keep the data streams flowing smoothly.
VV Block Size must meet the following constraining requirements:
• It must be an integer multiple of the Media Block Size.
• The PV Section Length (Media Block Size (MBS) * Blocks Between Tape Marks (BBTM)
divided by the VV Block Size (VVBS) must be a whole number. For example, if the Media
Block Size (MBS) is 64 KB, and the Blocks Between Tape Marks (BBTM) is 512, the physical
volume section length is 32 MB. The VV Block Size (VVBS) could be 64 K, 128 K, 256 K, or
larger, but not 192 K.
See the HPSS Installation Guide , Section 3.10.1.2: Virtual Block Size Selection (disk) and Section
3.10.1.3:Virtual Block Size Selection(tape) for information.
Stripe Width (SW). The number of Physical Volumes in a Virtual Volume in this Storage Class.
PV Size (PVSIZE). The estimated size of the tape volume in bytes. The actual number of bytes that can
be written to a tape will vary with individual media and data compressibility. Think of this field as the
nominal length of a tape of this type.
VV SIZE (VVSIZE). The virtual volume size. The product of the PV Size (PVSIZE) and the Stripe
Width (SW).
Stripe Length (SL). The Stripe Length (SL) is the product of the VV Block Size (VVBS) and the
Stripe Width (SW).
Transfer Rate
Device I/O Rate (DIOR). The approximate data transfer speed, in kilobytes per second (KB/sec), which
can be achieved by devices corresponding to Media Type.
Advice - This field is used in calculating a reasonable setting for Seconds Between Tape Marks
(SBTM).
Stripe Transfer Rate (STR). The estimated aggregate transfer rate for volumes of this type. This field is
calculated using the Stripe Width (SW) times the Device I/O Rate (DIOR).
Seconds Between Tape Marks (SBTM). The number of seconds between tape mark writes while
writing continuously to tape.
Advice - The Device I/O Rate (DIOR), the Media Block Size (MBS) and the Seconds Between Tape
Marks (SBTM) determine the length of a physical volume section. The administrator should set the
Device I/O Rate (DIOR) to an appropriate value for the device, and then pick a Media Block Size
(MBS). Finally, adjust the Seconds Between Tape Marks (SBTM) to strike a balance between tape
utilization and transfer efficiency.
Smaller values of Seconds Between Tape Marks (SBTM) cause more tape to be consumed in tape marks
and break up data streaming throughput on streaming tape drives, but cause controller buffers to be
flushed more frequently and may improve access times to the middle of large files.. Larger values
improve transfer efficiency. However, smaller values may reduce the amount of data that may need to be
re-written on another tape when a tape reaches EOM. As tape drive streaming rates increase, we
generally recommend larger values for this setting.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 165