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
DB Log Monitor Interval. The Core Server will check consistency of Database Logs and Backup Logs
at the indicated interval, specified in seconds. The logs are consistent if both primary and backup log
directories exist and contain log files with the same names. The minimum value for this field is 300
seconds (5 minutes). A value of 0 will turn off DB Log monitoring. This field may be overridden on the
Storage Subsystem configuration.
COS Change Stream Count. The number of background threads that run in the Core Server to process
Class of Service change requests. If a value of 0 is specified, the Global Configuration setting will be
used for this storage subsystem.
4.2.3.1. Create Storage Subsystem Metadata
Before creating the subsystem metadata, you must have created the subsystem database that will be used
by the subsystem and have created appropriate tablespaces for the database.
You should review and perform the steps in the following sections in the HPSS Installation Guide before
allocating metadata space for the new subsystem:
• 2.3.3 HPSS Storage Subsystems
• 3.5.2 HPSS Infrastructure Storage Space
• 3.5.3 HPSS Filesystems
• 3.5.4 HPSS Metadata Space
• 5.3.2 Install and Configure HPSS – Secondary Subsystem Machine
4.2.3.2. Create Storage Subsystem Configuration
Use the following steps to create a storage subsystem configuration:
1. Decide on a unique descriptive name for the new storage subsystem. SSM will automatically
choose the name “Subsystem #N”, where N is the subsystem ID selected by SSM. The name of
the new storage subsystem may be changed by the administrator at subsystem configuration time
only.
2. From the Health and Status window, select Configure/Subsystems from the menu. You will then
be presented a window that lists currently configured subsystems. Select the Create New button to
bring up another window to configure the new subsystem.
3. Enter the name you have chosen for the subsystem in the Subsystem Name field and enter the ID
of the subsystem in the subsystem ID field. Enter the name of the database you have chosen to
contain the tables for this subsystem in the Database Name field.
4. Decide which Classes of Service are to be supported by the new storage subsystem. SSM will
automatically select all Classes of Service to be supported, but the administrator can modify these
choices at any time. Also decide on a default Class of Service for this storage subsystem. By
default SSM leaves this field blank, which means that the default Class of Service specified in the
global configuration will apply to the new storage subsystem as well. The administrator may
choose to override the global value by using the subsystem configuration value at any time.
5. Decide whether gatekeeping or account validation are needed for this storage subsystem. If either
is required, a Gatekeeper will need to be configured for this storage subsystem. If the required
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 79