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
For IRIX systems, SCSI attached tape drives are typically referred to by pathnames of the form /dev/rmt/
tpsXdYns, where X is the SCSI controller number, and Y is the SCSI ID of the drive. Note that for Ampex
DST drives, the tpsXdYnrns name should be used (indicating that the driver should not attempt to rewind
the drive upon close). For other drives on IRIX, the tpsXdYnsvc name should be used (indicating that the
driver allows compression and variable block sizes).
For Solaris systems, SCSI attached tape drives are typically referred to by pathnames of the form
/dev/rmt/Xc, where X begins at zero and is incremented for each tape drive detected (the ‘c’ indicates
that compression is enabled). In particular note that the device that contains a ‘b’ in the name should
NOT be used, as this will change the behavior of the drive and cause the HPSS Mover to fail.
For Linux systems, this is the name that will be used to provide access to the SCSI raw device. The
pathname will be in the form /dev/raw/rawX, where X specifies the raw device number. You can run the
“raw -q -a” command to determine the correct raw device mappings. SCSI tape devices are referred to
by pathnames of the form /dev/stX, where X begins at zero and is incremented for each LUN detected.
Media Block Size (disk only). The block size for the device. This value should be a multiple of the
underlying disk block size; otherwise an error will occur at first I/O.
Bytes on Device (disk only). The size of the device in bytes.
Advice - The storage class to which this drive will be assigned must have a PV Size less than or equal to
this value.
If the Starting Offset is non-zero, then the Bytes on Device value cannot be greater than the actual size of
the underlying device less the Starting Offset value.
If this value is modified after the disk has been imported into HPSS, it must be emptied, exported and re-
imported.
Starting Offset (disk only). The offset in bytes from the beginning of the disk logical volume at which
the Mover will begin using the volume. The space preceding the offset will not be used by HPSS. This
value should be a multiple of the Media Block Size.
Advice - In some cases, the operating system may maintain control information at the beginning of a disk
volume which should not be overwritten by HPSS. As a specific example, the AIX Logical Volume
Manager (LVM) currently writes a control block at the start of a logical volume that is required during
some operations on mirrored logical volumes (such as splitting the mirror in the case of a failing
physical disk). The Starting Offset field can be used to force the Mover to skip over that control block
before writing the HPSS volume label or any user data (consult AIX documentation to determine the size
of the LVM control block).
SAN ID (disk only). The ID for the SAN group. A group is a set of devices that are logically related,
with the primary characteristic being that all devices in group are accessible by all clients. Each group is
identified with this globally unique group id. It is assigned to all devices within a SAN group.
Device Flags. The following fields are the device flags used by the Mover.
• Read Enabled. An indication of whether the device is available for reading.
• Write Enabled. An indication of whether the device is available for writing.
• Locate Support (tape only). An indication of whether the device supports a high speed (absolute)
positioning operation.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 199