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 a DB2 database
- About adding backup selections to a DB2 policy
- About adding schedules to a NetBackup for DB2 policy
- 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
- About NetBackup for DB2 templates and shell scripts
- Performing backups and restores of DB2
- 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)
- 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
Creating shell scripts using bpdbsbdb2
bpdbsbdb2 is a NetBackup for DB2 command that initiates template-based, user-directed backup and recovery. It also generates DB2 shell scripts from the templates created by the backup wizard.
To create a shell script, issue this command with the following options:
bpdbsbdb2 -backup -g script_file_name -t template_name
where:
script file name | Generates a shell script from a template. Enclose script_file_name in quotation marks (" ") if it contains space characters. Do not use this option with this command's -r (for "run") option. |
template_name | Identifies the template. bpdbsbdb2 retrieves backup templates from a known location on the master server. Specify only the file name. |
Note:
The user needs to review and customize any and all scripts that are generated from templates. Generated scripts are intended to be modified for the user's environment and preferences. For example, settings such as passwords or catalog partition numbers are not generated in the template-to-script conversion, so they require manual editing. In addition, generated scripts do not handle all possible error and failure cases and should be used at your own risk.
Use the DB2CMD command processor to run the scripts that you generated for Windows. This processor is provided with DB2, DB2CMD C:\TEMP\SCRIPT.CMD.
An authorized DB2 user needs to run the scripts that are generated for UNIX.
The user needs to review and modify script execution permissions as desired.
For security purposes, user names and passwords are not included in generated scripts. Add them as needed.
The DB2 QUIESCE command is generated when the template option is specified. However, this command fails if your version is before DB2 V8.1.
When attempting a point-in-time restore, customize the time value. The command DB2 RESTORE ... TAKEN AT strictly interprets the specified time and succeeds only if a backup image with the same time exists. For more information, see your IBM DB2 documentation. This limitation does not exist for templates, which search for an appropriate image.
If a template enables roll-forward recovery, then roll-forward commands are generated for all partitions that are specified in the template, whether or not that partition is configured for roll-forward recovery.
If a script performs a roll-forward recovery, customize the DB2NODE variable. In single partition environments, this variable can typically be empty (for example, "DB2NODE="). In a multiple partition environment, set this variable to the catalog partition number.
More Information