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
13.2.3.1.2. Site Defined Account Apportionment Table
In UNIX-style accounting, the UID (as Account Index) maps only to a specific user. Some sites may
wish to apportion different percentages of the charges for a single UID among different project charge
codes, but without using site style accounting. HPSS does not provide a means to do this, but a site could
implement its own table and utilities to do so. Here is an example of an Account Apportionment Table
which a site might implement to do this:
UID % of (Project(s))
1478 75(DND) 25(CBC)
3152 45(DDI) 25(DND) 30(CBC)
5674 100(DDI)
... .................
The site would need to write utilities to tie the Apportionment table to the HPSS accounting report.
13.2.3.1.3. Maintaining Site Defined Accounting Files
Sites which require a site defined Account Map, Apportionment Table, or other accounting files must
develop tools to maintain and modify the files according to local accounting policies. Tools will be
necessary to change, add, or delete an HPSS Account Index and its associated information. Site
administrators must implement their own policies on what to do when an account is deleted, a user moves
to another project, or a user leaves the system.
Other needed mappings, if any, must be maintained by the site in the Account Map file. When Account
Validation is disabled, the site will need to maintain the user-to-account index mappings in the Account
Map file as well.
UNIX-style accounting changes of this nature are handled through the normal utilities that set up and
modify users and UIDs. A basic set of site-developed utilities are described in more detail below.
• Add a user and account. New entries can be made and the next available HPSS Account Index
number will be assigned from the free-list. The free-list will most likely consist of the last
assigned number plus one, but could include reclaimed index numbers if a site chooses to re-use
Account Index numbers that were previously assigned and no longer referenced. It is not likely
that a site will need to reclaim Account Index numbers, but it is an option.
• Delete a user. When a user is deleted from the Account Map, the HPSS files must be reassigned
to another HPSS Account Index. This should be done from the HPSS client interface side. The
update_flag should be set to true to indicate that this account index number can be reclaimed.
The reclaiming tool should check for files using the account number before reclaiming it. When
the Account Index is reclaimed, it can be put on the free-list to be re-used. It is important to keep
a copy of the Account Map that corresponds to the HPSS accounting snapshot of storage space in
use for that time period so that the proper site information can be matched.
• Delete account. When an account is deleted, it is handled in the same manner as when a user is
deleted.
• Modify account. The entries in the Account Map can be modified to correlate the Account Index
to different information, but care should be taken to keep a copy of the corresponding tables for
past HPSS accounting runs.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 337