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
Chapter 14. User Interfaces
This chapter configuration information for the user interfaces provided with HPSS for transferring files:
• Client Application Programming Interface (API)
• Parallel File Transfer Protocol (FTP) or PFTP
• HPSS Virtual File System (VFS) Interface
14.1. Client API Configuration
The following environment variables can be used to define the Client API configuration. The defaults for
these variables are defined in the hpss_env_defs.h file.
HPSS_API_AUTHN_MECH specifies which authentication mechanism may be used. The values may
be “krb5” or “unix”. The default is HPSS_CLIENT_AUTHN_MECH.
HPSS_API_BUSY_DELAY specifies the number of seconds to delay between retry attempts. Note that
this value is used both for retrying initialization operations (see HPSS_API_RETRIES) and Core Server
requests (See HPSS_API_BUSY_RETRIES). The default value is 15.
HPSS_API_BUSY_RETRIES specifies the number of retries to be performed when a request fails
because the Core Server does not currently have an available thread to handle that request. A value of
zero indicates that no retries are to be performed (i.e., the operation will be performed once), and a value
of -1 indicates that retries should be attempted until either the request succeeds or fails for another
reason. The default value is 3 (which will result in up to 4 attempts).
HPSS_API_DEBUG specifies whether to produce debug messages. If the Client API is compiled with
debugging enabled, any non-zero value in HPSS_API_DEBUG enables debug messages. Note that non-
numeric strings will be interpreted as zero. By default, these messages will go to the standard output
stream (but see HPSS_API_DEBUG_PATH).
HPSS_API_DEBUG_PATH specifies the destination of debug messages; default is “stdout”. If
HPSS_API_DEBUG_PATH is set to "stdout" or "stderr", debug messages will be written to the standard
output or standard error I/O streams, respectively. Otherwise, the value will be interpreted as the
pathname of a file. The Client API must be compiled with debugging enabled.
HPSS_API_DESC_NAME specifies the descriptive name used in HPSS log messages if the logging
feature of the Client API is enabled. The default value is “Client Application”.
HPSS_API_DISABLE_CROSS_REALM specifies cross-realm authentication. When cross-realm
authentication is disabled, a client will not be allowed to access directories which are located in another
security realm. The default value is zero (meaning that cross-cell authentication is enabled). To disable
cross realm authentication, HPSS_API_DISABLE_CROSS_REALM must be set to a numeric, non-zero
value.
HPSS_API_DISABLE_JUNCTIONS specifies whether junction traversal is enabled. When junction
traversal is disabled, a client will not be allowed to access directories which require traversal to the
directory via a junction. The default value is zero (meaning junction traversal is enabled). To disable
junction traversal, HPSS_API_DISABLE_JUNCTIONS must be set to a numeric, non-zero value.
HPSS_API_DMAP_WRITE_UPDATES specifies the frequency of cache invalidates that are issued to
the DMAPI file system while writing to a file that is mirror in HPSS. The value indicates the number of
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 339