Veritas NetBackup™ for DB2 Administrator's Guide
- Introduction to NetBackup for DB2
- Installing NetBackup for DB2
- Configuring NetBackup for DB2
- Overview of NetBackup for DB2 configuration
- About permissions for NetBackup for DB2 log files (UNIX)
- About configuring a backup policy for DB2
- About adding backup selections to a DB2 policy
- Configuring an application backup schedule
- Example application backup schedule
- Configuring automatic backup schedules
- Example automatic backup schedule
- About schedule properties
- NetBackup for DB2 backup types
- Performing a manual backup
- Reviewing the auto-discovered mappings in Host Management
- About backing up archive log files with the user exit program
- Configuring the run-time environment
- Creating a db2.conf file for use with the user exit program
- Creating a db2.conf file (vendor method)
- Configuring bp.conf files in a cluster environment
- Keywords for the db2.conf file
- NetBackup for DB2 environment variables
- Configuring the logon account for the NetBackup Client Service for NetBackup for DB2
- About NetBackup for DB2 templates and shell scripts
- Performing backups and restores of DB2
- NetBackup for DB2 backup overview
- About backups from the NetBackup master server
- About user-directed backups
- Using the Backup, Archive, and Restore interface to browse DB2 resources
- About browsing DB2 backup images with bplist
- Performing a database restore
- About an alternate restore
- Using Snapshot Client with NetBackup for DB2
- NetBackup for DB2 with Snapshot Client features
- About NetBackup for DB2 with Snapshot Client operations
- About the sequence of a NetBackup for DB2 backup operation with Snapshot Client methods
- About the sequence of a NetBackup for DB2 restore operation with Snapshot Client methods
- About database objects supported by advanced backup methods
- About multistreaming and DB2 snapshot backups
- About symbolic links and DB2 backups and restores (UNIX)
- NetBackup for DB2 stream-based operations
- NetBackup for DB2 file-based operations
- Example: multiple sessions for a DB2 snapshot backup
- About configuring Snapshot Client with NetBackup for DB2
- Configuration requirements for snapshot backups with NetBackup for DB2
- Configuring a snapshot policy for NetBackup for DB2
- About configuring the db2.conf for a snapshot policy
- Restoring NetBackup for DB2 from a snapshot backup
- About restoring individual files from a NetBackup for DB2 snapshot backup
- About NetBackup for DB2 restores of volumes and file systems using snapshot rollback
- Performing a NetBackup for DB2 point-in-time rollback restore from a SnapVault backup (UNIX)
- Performing a snapshot rollback restore from the Java or Windows interface
- Performing a snapshot rollback restore from the command line
- Troubleshooting NetBackup for DB2 rollback restores
- About configuring NetBackup for DB2 block-level incremental backups on UNIX
- How BLI works with NetBackup for DB2 (UNIX)
- About the Storage Checkpoint facility and NetBackup for DB2
- Configuration requirements for BLI backups with NetBackup for DB2
- Storage Checkpoint configuration on the NetBackup for DB2 client
- Configuring policies for BLI backups with NetBackup for DB2
- BLI incremental backup options using NetBackup for DB2
- About Snapshot Client effects
- Performing NetBackup for DB2 backups with Snapshot Client methods
- Performing NetBackup for DB2 restores with Snapshot Client methods
- Troubleshooting NetBackup for DB2
- NetBackup debug logs and reports
- Enabling the debug logs for a NetBackup for DB2 client automatically (Windows)
- Enabling the debug logs manually (Windows)
- Enabling the debug logs manually (UNIX)
- About the NetBackup for DB2 log files
- Setting the debug level on a Windows client
- Setting the debug level on a UNIX client
- About NetBackup server reports
- Minimizing timeout failures on large database restores
- Minimizing the loading and unloading of tapes for database backups
- Use the NET_BUFFER_SZ file to speed up a slow restore
- About false restore failures reported in the activity monitor
- About the error message codes
- Delays in completion of backup jobs
- Appendix A. Configuration for a DB2 EEE (DPF) environment
- Appendix B. Using NetBackup for DB2 with SAP®
- Appendix C. Register authorized locations
- Index
About an alternate restore
An alternate restore lets you restore a DB2 database to a different client or to a different instance. You can also change the name of the database during the restore.
Alternate restores differ from regular restores as follows:
Use the regular restore procedures if you want to restore a database into the same instance on the same NetBackup client that hosted it previously. In this case, the database also retains its original name.
Use alternate restore procedures if you want to restore a database to a different instance or to a different client or if you must rename the database during the restore.
Databases within an instance must have unique names. If you restore a database into an instance that already has a database by that name, the alternate restore process overwrites the existing database.
Table: Types of restores permitted summarizes the types of restores you can perform and whether you need to use regular or alternate restore procedures.
Table: Types of restores permitted
Object | Regular restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore | Alternate restore |
|---|---|---|---|---|---|---|---|---|
Database name | Same | Same | Same | Different | Same | Different | Different | Different |
Instance | Same | Same | Different | Same | Different | Different | Same | Different |
Client | Same | Different | Same | Same | Different | Same | Different | Different |
For example, assume that you have two NetBackup clients, grade7 and grade8. Instances class1 and class2 are on grade7. Instance class1 is on grade8.
Figure: Alternate restore example illustrates this example.
The following list shows some of the types of restores you can perform with alternate restore procedures:
You can restore database eng1 from instance class2 on client grade7 into instance class1 on client grade8. Database eng1 can retain its name because it is unique to instance class1.
You can restore database math1 from instance class1 on client grade7 into instance class1 on client grade8. During the restore, you need to rename math1 to math2 because class1 on grade8 already has a database named math1. Without renaming, the existing database math1 would be overwritten.
You can restore database art1 from instance class2 on client grade7 into instance class1 on client grade7. During the restore, you need to rename art1 to art2 because instance class1 already has a database named art1. Without renaming, the existing database art1 would be overwritten.