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 7. Device and Drive Management
Every disk and tape drive that is used by HPSS is controlled by two servers. The PVL controls mounts
and dismounts (for disk devices these are logical operations only), and the Mover controls I/O. In support
of these two views, the terms “PVL drive” and “Mover device” are used to refer to the configuration and
information maintained about the drive by the PVL and Mover, respectively.
The configuration information is all managed through a single SSM list window. However, there are
separate PVL drive and Mover device information windows, each with their own administrative state and
other settings. When administrative changes are made, it is important to know whether they are to be
performed against the PVL drive, the Mover device, or both.
Devices and drives are added and deleted dynamically. This means that they are added and deleted while
the system is UP. Specifically the PVL must be UP; additionally it is expected that the associated Mover
and associated PVR (for tape) are also UP. A new device and drive cannot be used until the PVL has
successfully informed the associated Mover and PVR (for tape) about the new device and drive.
Likewise, a previously deleted device and drive cannot be added back until the PVL has successfully
informed the associated Mover and PVR (for tape) about the delete. Likewise, a previously added device
and drive cannot be deleted until the PVL has successfully informed the associated Mover and PVR (for
tape) about the add. Further details are described in this chapter.
In general, devices and drives can not be updated dynamically (i.e. while the PVL, associated Mover and
associated PVR (for tape) are UP). However, there are some drive attributes for which the configuration
metadata can be updated dynamically via the PVL Drive Information window and there are some device
attributes for which the configuration metadata is not updated dynamically but the server “in memory”
values can be changed dynamically (but not preserved when the Mover is restarted) via the Mover
Device Information window. Further details are described in this chapter.
Note that all newly-created PVL drives are locked (i.e. the Devices and Drives window Drive Admin
State reports “Locked”), which prevents mounts from occurring on the drive. Therefore, the PVL drive
will need to be unlocked before the drive can be used. This can be done by highlighting the device/drive
in the Devices and Drives window and pressing the “Unlock” button under the Drive Administration
group heading.
Review the appropriate subsections of Section 5.1.1: Physical Volume Repository (PVR) Specific
Configuration on page 109 before configuring a device/drive or modifying its state.
7.1. Configure a New Device & Drive
Be certain all tape drives are configured to use variable block sizes (Section 7.1.2: Enable Variable Block
Sizes for Tape Devices on page 207). These steps are also covered in detail in the HPSS Installation
Guide. Section 3.7.7.2: Tape Devices.
The Device and Drive configuration entry can be created and managed using the Devices and Drives
window (Section 7.1.1: Devices and Drives Window on page 202).
After a drive has been configured, its state can be changed (unlocked/locked) using the state change
instructions described in Section 7.1.1: Devices and Drives Window on page 202.
Before adding a tape drive to HPSS, the administrator must first fully configure the tape hardware and
driver software into the host platform and operating system. For disk drives, the raw disk must first be
defined in the operating system. Note that using the block special file name in the device configuration
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 196