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
An accounting policy is required whether the site actually charges users for HPSS usage or not.
Field Descriptions
Accounting Style. The style of accounting that is used by the entire HPSS system. Valid values are SITE
or UNIX. The default value is UNIX.
Under UNIX style accounting, resource usage is reported by user ID (UID). Each user is allowed to use
only one account ID, which has the same numerical value as his user ID. Under SITE style accounting,
each user may user multiple account IDs.
Note that if you use SITE style accounting, you must either enable Account Validation in the
Accounting Policy or select LDAP as your authorization mechanism. See below for a description of the
Account Validation field in the Accounting Policy. See section 2.1:Security Services on page 21for a
description of LDAP and other HPSS authorization mechanisms. See the HPSS Installation Guide,
section 3.9.3: Accounting Policy and Validation for a complete description of accounting styles and
account validation.
Advice - This field must be set up properly before any files are written to the system. Under UNIX-style
accounting, HPSS obtains the account number from the user’s UNIX UID. Site-style accounting allows
the account ID to be set independently of the UNIX UID. Once the accounting policy is configured, the
Accounting Style cannot be changed.
Storage Unit Size. The integral units to be displayed in the report file. The valid values for this field are
Bytes, Kilobytes, Megabytes, and Gigabytes. The default value is Bytes.
Status Message Interval. The number of seconds between status messages sent to SSM by the
Accounting utility during an accounting run. A non-zero value less than 10 will be treated as 10. A value
of 0 will prevent accounting status messages from being generated. The default value is 30 seconds.
Pathname of Executable (UNIX). The UNIX path name of the accounting utility executable. This field
may contain any valid UNIX path name. The default value is “/opt/hpss/bin/hpss_acct”.
Report File (UNIX). The UNIX pathname where the generated accounting report will be stored. The
Report File (UNIX) field can contain any valid UNIX pathname. The default value is
“/var/hpss/acct/acct_report”.
Comment File (UNIX). A UNIX pathname of an optional commentary text file. The contents of this file,
if it exists, are prepended to the Report File (UNIX) at the end of a successful accounting run. The data
field may be left empty to indicate that a comment file will not be used or it may contain any legal UNIX
pathname. The default value is “/var/hpss/acct/acct _commentary”.
Options:
Account Validation. A flag that indicates whether or not authorization of user accounts should be
performed by a Gatekeeper. The default value is OFF.
Advice - If you turn this flag ON, you must configure at least one Gatekeeper which will perform the
account validation service.
Require Default Account. A flag that indicates whether or not users must have a valid default account
index before they are allowed to perform any operation. The default value is OFF. It is only used if
Account Validation has been enabled. If this flag is disabled, validation will occur only during file
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 331