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 a db2.conf file for use with the user exit program
The NetBackup for DB2 configuration file, db2.conf, consists of a series of keywords and values. This file defines how to back up the database and the archive logs. It must be created on each NetBackup for DB2 client.
The installation package installed a file named db2.conf that you can customize. The following procedures show you how to customize this file. Follow the instructions in this section if you use the user exit program to perform backups.
To create a db2.conf file for use with the user exit program
- Before you create the db2.conf file, you need to create the policies to back up the archive logs and the configuration files.
- Log on to a client computer.
- Copy the sample db2.conf file from its location in the sample directory to its active location.
Its location in the sample directory is as follows:
The active location for the db2.conf file is as follows:
- In the db2.conf file, create an object identifier for backing up the database.
This object identifier starts with the following keyword lines:
DATABASE SAMPLE OBJECTTYPE DATABASE ...
- In the db2.conf file, create an object identifier for backing up the archive logs.
The form depends on how the archive logs are backed up, as follows:
If you use ARCFUNC SAVE:
DATABASE SAMPLE OBJECTTYPE ARCHIVE
POLICY WIN_TYPE_POL_LOGPOL # an MS-Windows-NT type policy
POLICY STD_TYPE_POL_LOGPOL # a standard UNIX type policy
In the POLICY line, specify the name of the MS- Windows or Standard policy for backing up the archive logs.
In the SCHEDULE line, specify the User Backup schedule that you created earlier for backing up the archive logs.
If you use ARCFUNC COPY:
DATABASE SAMPLE OBJECTTYPE ARCHIVE
Windows: ARCDIR C:\MyLogs\arcdir\ RETDIR C:\MyLogs\arcdir\
UNIX: ARCDIR /home/db2inst1/arcdir RETDIR /home/db2inst1/arcdir
In the ARCDIR line, specify the full path to the location of the archive logs.
In the RETDIR line, specify the full path to the location from which the archive logs are retrieved. Typically, the RETDIR location is the same as the ARCDIR location.
- You may need to add other entries to the db2.conf file.
- Save and close the db2.conf file.
- Repeat this procedure on each client computer.