Veritas NetBackup™ for DB2 Administrator's Guide
- Introduction to NetBackup for DB2
- Installing NetBackup for DB2
- Verifying the operating system and platform compatibility
- About log archiving
- Configuring NetBackup for DB2
- About configuring a backup policy for DB2
- About adding backup selections to a DB2 policy
- 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
- About NetBackup for DB2 templates and shell scripts
- Creating DB2 scripts manually
- Performing backups and restores of DB2
- About user-directed backups
- Performing a database restore
- About an alternate restore
- Using Snapshot Client with NetBackup for DB2
- About NetBackup for DB2 with Snapshot Client operations
- Restoring NetBackup for DB2 from a snapshot backup
- About configuring NetBackup for DB2 block-level incremental backups on UNIX
- Configuring policies for BLI backups with NetBackup for DB2
- About Snapshot Client effects
- Troubleshooting NetBackup for DB2
- About the NetBackup for DB2 log files
- 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
To create a shell script, issue this command with the following options:
bpdbsbdb2 -backup -g script_file_name -t template_name
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.
Identifies the template.
bpdbsbdb2 retrieves backup templates from a known location on the master server. Specify only the file name.
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.
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.