You can also use the 'db2ckbkp' utility to determine the full backup
image directory structure if it wasn't supplied:
C:\Backups>db2ckbkp -H 172030.001
=====================
MEDIA HEADER REACHED:
=====================
Server Database Name -- SAMPLE
Server Database Alias -- SAMPLE
Client Database Alias -- SAMPLE
Timestamp -- 20040114172030
Database Partition Number -- 0
Instance -- DB2
Sequence Number -- 1
Release ID -- A00
Database Seed -- 4035829E
DB Comment's Codepage (Volume) -- 0
DB Comment (Volume) --
DB Comment's Codepage (System) -- 0
DB Comment (System) --
Authentication Value -- 255
Backup Mode -- 0
Includes Logs -- 0
Compression -- 0
Backup Type -- 0
Backup Gran. -- 0
Status Flags -- 15
System Cats inc -- 1
Catalog Partition Number -- 0
DB Codeset -- IBM-1252
DB Territory --
LogID -- 1074118829
LogPath --
D:\DB2\NODE0000\SQL00001\SQLOGDIR\
Backup Buffer Size -- 8876032
Number of Sessions -- 1
Platform -- 5
The proper image path would be:
SAMPLE.0\DB2\NODE0000\CATN0000\20040114\172030.001
Image header dumped -- NO VERIFICATION PERFORMED.
Hope that helps.
kdr
Ian wrote:
Talk to your hosting site -- for a Windows platform, you need the entire
path to exist in order to restore.
For a backup taken with the command 'backup database cw to c:\db2backup',
The path would look something like:
c:\db2backup\CW.0\DB2\NODE0000\CATN0000\20040219\0 30327.001
On your server, you need the same directory structure from CW.0 on down.
--
================================================== ===================
Kelly D. Rodger IBM Canada
DB2 UDB Development Backup & Restore
================================================== ===================