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
information contained in the internal label will not match the side information passed to PVL in the
Import request. If the start of the OwnerID field is not “HPSS”, then the volume will be imported as a
Foreign Label volume and the side will be set to zero.
When importing a non-removable disk volume into HPSS, the raw disk must already be defined in the
host system. The import labels the volumes with HPSS labels.
The volumes can be imported into HPSS using the Import Disk Volumes window (Section 8.1.1.3 on
page 230) or the Import Tape Volumes window in the following section. Once the volumes are imported,
the HPSS storage space can be created using the Create Disk Resources or Create Tape Resources
window.
The import step must be done for both disk and tape volumes. Ensure that the PVL, PVR, and
appropriate Movers are up and running before initiating a requesting for the import operation. Also,
ensure that SSM is connected to the PVL.
When importing tapes, the maximum number of tape drives used by the import process is controlled by
the Max Number of Drives field in the Import Tape Volumes window. Each tape must be mounted and
its label must be written or checked. The PVL will attempt to evenly distribute the work across the
specified number of tape drives. The administrator should consider the current and expected demand for
tape drives of the type needed for the import, when setting this field.
When imports to an operator PVR are performed, requests to mount the tape cartridges are serialized.
This is necessary to ensure proper labeling of unlabeled tapes. Any unlabeled cartridge mounted in a
drive under control of the operator will be assumed to be the requested cartridge. Because any tape that is
mounted will be labeled without machine checking of the external label, this operation is not without
risk. It is strongly recommended that labeling of cartridges be performed by a robot that can verify the
external label of a cartridge, if possible.
When SSM completes the import request, it reports the number of volumes imported in the window
status field. Any error causes SSM to stop processing the request. If the reported number is less than the
number requested, you should retry the import request after first addressing the reason for the initial
failure. For the retry, the original list of volumes to import can be re-used because the PVL will skip
volumes that have already been imported.
8.1.1.1. Import Tape Volumes Window
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 225