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.