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
- 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
About browsing DB2 backup images with bplist
You can use the bplist command to search DB2 backup images. The output from bplist differs depending on how you manage your archive log files.
Table: bplist output
bplist option | Description |
|---|---|
-t 18 | This example searches all DB2 backup images for a client named camel, which is also the master server. The information comes from the NetBackup catalog on the master server. The user exit program backs up the archive files. The bplist -t 18 option specifies the DB2 backup type. The bplist output shows the DB2 database backup images that are stored in the NetBackup database. Windows: install_path\NetBackup\bin\bplist -C camel -S camel -t 18 -R / DB2:\SAMP\node0000\2009120210515\SAMP.0.DB2.node0000.0.2009120210515.1 DB2:\SAMP\node0000\2009120210473\SAMP.0.DB2.node0000.0.2009120210473.1 DB2:\SAMP\node0000\2009112915411\SAMP.3.DB2.node0000.4.2009112915411.1 UNIX: /usr/openv/netbackup/bin/bplist -C camel -S camel -t 18 -R / /DB2/SAMP/node0000/2009120210515/SAMP.0.DB2.node0000.0.2009120210515.1 /DB2/SAMP/node0000/2009120210473/SAMP.0.DB2.node0000.0.2009120210473.1 /DB2/SAMP/node0000/2009112915411/SAMP.3.DB2.node0000.4.2009112915411.1 Where: DB2 is the directory name for all DB2 backups. SAMP is the name of the database (both occurrences). node0000 is the node name. 20091202105150 is the time that the backup occurred. 0 is the type of backup taken. Zero (0) indicates a full database backup. Three (3) indicates a tablespace backup. DB2 is the database instance name. It is one to eight characters in length. node0000 is the node number. In non-partitioned database systems, the node number is always zero (node0000). In partitioned database systems, the number is nodexxxx, where xxxx is the number assigned to the node in the 0 is the last archive log number. 20091202105150 is the timestamp, which includes the date (year, month, day) and time (hour, minute, second). 1 is the session number. This file extension identifies the session number that was specified on the DB2 BACKUP command. |
-k DB2_Log_Policy | This example searches all DB2 backup images for a client named cow, which is also the master server. The information comes from the NetBackup catalog on the master server. This example assumes that the user exit program is used to back up the archive files. The -k DB2_Log_Policy option specifies the files that are backed up with this policy. The policy name originates from the settings in the db2.conf file for archive log files. The bplist output shows the list of DB2 archive log files that are stored in NetBackup. Windows: install_path\NetBackup\bin\bplist -k DB2_Log_Policy -C cow -S cow -R / C:\DB2\NODE0000\SQL00001\SQLOGDIR\S0000026.LOG C:\DB2\NODE0000\SQL00001\SQLOGDIR\S0000025.LOG C:\DB2\NODE0000\SQL00001\SQLOGDIR\S0000024.LOG UNIX: /usr/openv/netbackup/bin/bplist -k DB2_Log_Policy -C cow -S cow -R / /home/db2inst/NODE0000/SQL00001/SQLOGDIR/S0000026.LOG /home/db2inst/NODE0000/SQL00001/SQLOGDIR/S0000025.LOG /home/db2inst/NODE0000/SQL00001/SQLOGDIR/S0000024.LOG |
-k log_policy | This example uses bplist to search the DB2 archive log files for a client named cow. The -k log_policy option specifies the files that are backed up with this policy. The VENDOR is set and the user exit program is not used to back up the archive logs: Windows: install_path\NetBackup\bin\bplist -C cow -S cow -k log_policy -R / Example location:C:\DB2\SAMPLE\LOGFILE\node0000\db2v864d\C0000000_S0000000.LOG UNIX: /usr/openv/netbackup/bin/bplist -C cow -S cow -k log_policy -R / Example location:/DB2/SAMPLE/LOGFILE/node0000/db2v864d/C0000000_S0000000.LOG Where: DB2 is the directory name for all DB2 backups. SAMPLE is the name of the database. LOGFILE identifies the entry as a log file. node0000 is the node name. db2v864d is the name of the DB2 instance. C0000000_S0000000.LOG is the name of the log file that DB2 provides. |
You can find more information on the bplist command in the NetBackup Commands Reference Guide.