02-27-2013 06:29 PM
NBU Version 7.1.0.4 (Linux)
Hi all,
We are just starting to use the DB2 agent in our environment, and wanted to find out about verifying DB2 backups using the db2ckbkp command. I have read all the guides I can but haven't been able to find the information.
As per process of obtaining the DB2 backup list we run the following command - bplist -C <Client> -t 18 -l -R /
This gives us the following output.
-rw-rw-r-- db2inst1 staff 137610056K Jan 23 11:31 /DB2/TESTDB/node0000/20130123113137/TESTDB.0.db2inst1.node0000.0.20130123113137.1
What I want to know is if it is possible to somehow verify this image from DB2 using the db2ckbkp command?
Previously we would run the following command against an image to get the header information.
db2ckbkp -h SAMPLE2.0.TEST.NODE0000.CATN0000.19990818122909.001
=====================
MEDIA HEADER REACHED:
=====================
Server Database Name -- SAMPLE2
Server Database Alias -- SAMPLE2
Client Database Alias -- SAMPLE2
Timestamp -- 19990818122909
Database Partition Number -- 0
Instance -- test
Sequence Number -- 1
Release ID -- 900
Database Seed -- 65E0B395
DB Comment's Codepage (Volume) -- 0
DB Comment (Volume) --
DB Comment's Codepage (System) -- 0
DB Comment (System) --
Authentication Value -- 255
Backup Mode -- 0
Include Logs -- 0
Compression -- 0
Backup Type -- 0
Backup Gran. -- 0
Status Flags -- 11
System Cats inc -- 1
Catalog Database Partition No. -- 0
DB Codeset -- ISO8859-1
DB Territory --
LogID -- 1074717952
LogPath -- /home/db2/test/NODE0000/
SQL00001/SQLOGDIR
Backup Buffer Size -- 4194304
Number of Sessions -- 1
Platform -- 0
Any help would be greatly appreciated.
Solved! Go to Solution.
02-28-2013 11:52 AM
What I want to know is if it is possible to somehow verify this image from DB2 using the db2ckbkp command?
Sorry, but the (overly simplified) answer is "no."
02-28-2013 11:52 AM
What I want to know is if it is possible to somehow verify this image from DB2 using the db2ckbkp command?
Sorry, but the (overly simplified) answer is "no."
02-28-2013 02:14 PM
Thanks Chris.