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
is On Open. For all subsequently created COSes, the default value is the same as the most recent COS
configured.
Advice – Changing the Stage Code should be done with care. See Section 6.3.3: Changing a Class of
Service Definition on page 178 for detailed information on each of the choices for Stage Code.
Minimum File Size. The size, in bytes, of the smallest bitfile supported by this COS. Valid values are
any positive 64-bit integer value.
Maximum File Size. The size, in bytes, of the largest bitfile supported by this COS. Valid values are any
positive 64-bit integer value.
Allocation Method. How disk storage segments will be allocated in the storage class at the top level of
the hierarchy used by this COS. Ignored if the top level storage class is tape. Three allocation methods
are available:
● Fixed Length, Classic Style. All storage segments allocated for a single file, except possibly the
last segment of the file, are the same size. This size is computed at file creation time to be the
size which wastes the least disk space, based on the file size, the minimum and maximum
segment sizes configured for the storage class, and the average number of segments per file
configured for the storage class. In order to take maximum advantage of this allocation method,
the application creating the file must specify the file size in its file creation hints.
The application can force this fixed segment size to be the maximum segment size configured for
the storage class by specifying HINTS_FORCE_MAX_SSEG in the file creation hints.
If the application does not force the segment size to be the max size and it does not provide hints
telling the core server the file size, then the core server will use the minimum segment size
configured for the storage class.
If the file is purged completely from the top level and later restaged to the top level, a new
segment size will be computed at stage time based on the current file size.
● Fixed Length, Max Style. The size of each storage segment allocated for a file, except possibly
the last segment, is the maximum segment size configured for the storage class.
● Variable Length. The size of the first storage segment allocated for a file is the minimum
segment size configured for the storage class. The size of each successive storage segment is
twice that of the preceding segment, up to the maximum segment size configured for the storage
class. Once the max segment size is reached, each remaining segment except possibly the last is
also the max segment size.
Under all three allocation methods, the last segment of the file may be truncated to a size to best fit the
actual data contained in the segment. See the Truncate Final Segment option in the Class Flags
section below.
Class Flags
• Enforce Maximum File Size. When set, a bitfile larger than the Maximum File Size cannot be
created in this COS.
• Force Selection. A flag to determine how a COS will be selected. If ON, a client must explicitly
select this COS in order to have a file assigned to it; if the client merely supplies general COS hints
for a file, this COS will not be selected.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 176