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
requesting client to the AML’s storage positions, drives, and Insert/Eject units. Access configurations for
clients are set in the configuration file C:\DAS\ETC\CONFIG on the OS/2 PC. The client name can be up
to 64 alphanumeric characters in length and is case sensitive.
Server Name. TCP/IP host name or IP address of the AML OS/2-PC DAS server. This value must be
defined in the network domain server and must be resolvable during DAS start. The server name is set in
the configuration file C:\CONFIG.SYS on the OS/2 PC. The server name can be up to 64 alphanumeric
characters long and can include up to six dots (‘.’).
5.1.1.2.1. AML PVR Additional Information
The AML PVR is supported by special bid only.
ADIC Automatic Media Library Storage Systems Information
HPSS can share an AML robot with other tape management systems. If a robot is shared, care must
be taken to make sure that a drive is not used by any other tape management system while that drive is
configured as unlocked in HPSS. This is important because HPSS can be configured to periodically poll
all of its unlocked drives even if they are not currently mounted or in use by HPSS. If a drive is being
used by another tape management system, it must be configured as locked in HPSS. For robots that have
more than one arm (such as the AML/2), users should configure the PVL Drive Information/Controller
ID of each drive depending on which arm is servicing it.
User needs to set the Server Name and Client Name, which are case sensitive, in the AML PVR Server
Configuration panel to establish the connectivity between the HPSS software and the OS/2 controlling
the robot. The Server Name is the name of the controller associated with the TCP/IP address, as defined
in the TCP/IP HOST file, and the Client Name is the name of the OS/2 administrator client as defined in
the DAS configuration.
Additionally users must configure the Insert/Eject ports for the AML PVR using the configuration files /
var/hpss/etc/AML_EjectPort.conf and /var/hpss/etc/AML_InsertPort.conf. The reasons are that the AML
robot can have multiple insert and eject ports, which have the capability to handle different media types.
These two configuration files in conjunction with the AMU AMS configuration files specify which
Insert/Eject areas or bins the tapes should be placed in for insertion into the archive and where they are
ejected to when the HPSS export command is used.
Note that if multiple E/I/F bins are used for exporting cartridges, users must set the environment variable
DAS_EJECTAREAFULL=1 on the DAS Server PC by doing the following:
1. Edit the config.sys
2. Add a new line:
set DAS_EJECTAREAFULL=1
Starting the DAS Server Processes
In order for the HPSS AML PVR to communicate with the AML robot, it is required that the DAS Server
process be running.
Once the DAS, TCP/IP and AML configuration have been completed, the DAS server is initialized and
started with the following steps:
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 115