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 15. Backup and Recovery
This chapter discusses the following operations:
• Backup and recover HPSS metadata
• Backup HPSS environment
• Recover HPSS user data
• Handling DB2 space shortage
15.1. HPSS Metadata Backup and Recovery
Each HPSS site is responsible for implementing and executing the HPSS metadata backup and recovery
process. The HPSS administrator must ensure that HPSS metadata is backed up on a regular basis. In
addition, the HPSS administrator must verify that the backup files can be used to restore the HPSS
metadata up to the point of failure. Sites can choose to use a commercially available backup software
tool, such as the Tivoli Storage Manager (TSM), to backup the HPSS metadata. Optionally, a set of
simple and customizable backup scripts can be developed to backup the HPSS metadata. Contact your
HPSS Support Representative to obtain sample backup scripts and guidance for implementing the DB2
backup process for your site.
The following sections provide an overview of the metadata backup and recovery process.
The backup topics provided in the following sections are meant only as an overview. The DB2
Data Recovery and High Availability Guide and Reference should be consulted in order to
obtain a complete understanding and explanation of issues and procedures associated with
enabling full recoverability of DB2 data.
15.1.1. HPSS Administrator Responsibilities for DB2
While DB2 has sophisticated backup and recovery abilities, it is fundamentally the responsibility of the
HPSS administrator to ensure that these facilities are configured and working correctly. This section
outlines some of those responsibilities.
While storing the DB2 data tables on reliable disk storage systems can be very useful if it becomes
necessary to recover the database, it is essential that the database be backed up regularly, and that the
backup media be reliable. Many sites keep multiple copies of the backup media in separate locations. It
is also extremely important that site administrators verify that they can restore a failed database from the
backup media. Time should be scheduled on an occasional basis to perform practice recoveries from the
backup media. This could be done by creating a separate instance of the HPSS DB2 system on a separate
computer and restoring it from the primary instance backup media.
HPSS databases should be backed up regularly. Most sites back up the entire database once each night,
using the online backup procedure. Note that On-line backups are only available for database
configurations that enable log archiving. (see section 15.1.2.1 Configuring DB2 for Online Backup on
page 358). Online backups do not interfere with normal HPSS processing. It is equally important to
monitor the online backup process and verify it is completing normally.
As HPSS operations take place, DB2 writes transaction log entries describing the changes that have been
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 356