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
write operations between cache invalidates. The default value is 20.
HPSS_API_HOSTNAME specifies the hostname to be used for TCP/IP listen ports created by the
Client API. The default value is HPSS_HOST. This value can have a significant impact on data transfer
performance for data transfers that are handled by the Client API (i.e., those that use the hpss_Read and
hpss_Write interfaces). The default is HPSS_HOST.
HPSS_API_LIMITED_RETRIES specifies the number of retry attempts before a limited retry error
operation fails. Currently, no operations are defined as "limited retry error operations". The default value
is 1.
HPSS_API_MAX_CONN specifies the number of connections that are supported by the Client API
within a single client process. If HPSS_API_MAX_CONN is set to zero, the number of connections is
equal to the default supported by the HPSS connection management software - currently 20. If
HPSS_API_MAX_CONN is nonzero, it is the number of connections to be used.
HPSS_API_RETRIES specifies the number of retries to attempt when an operation fails. Currently this
class of operation includes library initialization and communications failures. A value of zero indicates
that no retries are to be performed (i.e., the operation will be attempted once), and value of -1 indicates
that the operation will be retried until successful. The default value is 4 (meaning the operation will be
attempted up to five times).
HPSS_API_RETRY_STAGE_INP specifies whether retries are attempted on attempts to open files in a
Class of Service that is configured for background staging on open. A numeric, non-zero value (the
default) indicates that opens which would return -EINPROGRESS to indicate that the file is being
staged will be retried (using HPSS_API_RETRIES and HPSS_API_BUSY_DELAY to control the
number and timing of retries), while a value of zero indicates that the -EINPROGRESS return code will
be returned to the client. The default value is "1".
HPSS_API_REUSE_CONNECTIONS specifies whether TCP/IP connections are to be left open as
long as a file is open or are to be closed after each read or write request. A numeric, non-zero value will
cause connections to remain open, while a value of zero will cause connections to be closed after each
file access. The default value is zero.
HPSS_API_RPC_PROT_LEVEL specifies the RPC protection level. Valid values are “connect”,
“packet”, “packet integrity”, and “packet privacy”. The default is HPSS_RPC_PROT_LEVEL.
HPSS_API_SAN_3P specifies whether to enable SAN3P transfers. Valid values are “on” an d “off”.
The default is on.
HPSS_API_SITE_NAME specifies the site name to be used when initializing the HPSS security
services. The default value is HPSS_SITE_NAME .
HPSS_API_TOTAL_DELAY specifies the number of seconds to continue retrying requests. A value of
zero indicates that no there is no time limit. The default value is zero.
HPSS_API_USE_PORT_RANGE specifies whether the HPSS Mover(s) should use the configured port
range when making TCP/IP connections for read and write requests. A numeric, non- zero value will
cause Movers to use the port range, while a value of zero will cause Movers to allow the operating
system to select the port number. The default value is zero.
HPSS_KRB5_KEYTAB_FILE specifies the name of the file containing the security keys necessary for
successfully initializing the Client API for Kerberos authentication. The default is auth_keytab:/var/hpss/
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 340