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
Advice - This option is supported for 3590, 3590E, 3580, 3592, 9840, 9940, DST-312, DST-314,
T10000 and GY-8240 devices.
• NO-DELAY Support (tape only). An indication of whether the device supports opening the device
with no delay flag set, while allowing tape I/O operation after the open.
Advice - On some tape devices, this will allow for a quicker polling operation when no tape is
presently loaded in the device. This field is meaningful for tape devices only.
• Write TM(0) to Sync (tape only). An indication of whether the device supports issuing a write
tape mark request with a zero count to flush data written previously to the tape media.
Advice - On some devices, this may provide a higher performance method to ensure that data has
been safely written to the media. This option is not used for the IBM 3590 and 3590E devices,
provided the HPSS supported device driver is used in accessing the device. Note that for Ampex
DST-312 this field should be set to “ON”.
• Removable Media Support (tape only). An indication of whether the device supports removable
media.
• SCSI-2 LBA Positioning (tape only). If ON, the tape device supports SCSI-2 Logical Block
Addresses.
Advice - If SCSI-2 LBAs and the SCSI LOCATE command (Locate Support) are supported by the
device, HPSS will calculate tape read addresses based on known LBAs and relative addresses.
LBA positioning provides for faster access of data residing on tape. The benefit will be realized
for read requests with many source descriptors specifying locations spread sparsely down the
tape. This is supported only by the IBM SCSI tape device driver.
• SAN3P-transfer Enabled (disk only). If ON, SAN3P data transfers to this device will be
supported.
Warning – There is a security vulnerability associated with the use of SAN3P. If a user is root on
a machine which has access to the SAN (e.g. a client machine) then that user has the potential to
access or destroy fiber-channel connected disk storage. Two areas of concern: 1) verification
that only authorized users (usually limited to only ‘root’ or ‘hpss’) are granted read and
write access to these resource; 2) HPSS administrators should be aware that machines,
possibly owned or managed by other groups, which are added to the SAN to facilitate the
use of SAN3P transfers will have access to all data on disk and tape resources. If those
systems are compromised, or there are individuals authorized for systems privileges on
those particular machines, but not necessarily authorized for HPSS administrative access,
there is the potential for access and/or damage to HPSS data. These are inherent
limitations of SAN implementations that have not yet been addressed by the industry and
cannot be remedied by HPSS.
• Multiple Mover Tasks (disk only). If ON, the Mover will allow multiple Mover tasks to access
the disk device.
• Reserve/Release (tape only). An indication of whether a SCSI reservation is taken on the device
when it's opened.
Advice - This is useful on fiber attached tape devices to ensure that HPSS has sole control on the
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 200