Ignite "make_recovery" tape script

[Al Jordan]

I'm using the latest 22160 Ignite software on HP 10.20 on a HP-C200. I've been
able to run the make_recovery script and successfully create duplicate client
machines. But, my duplicate server recovery reports a large change in the
blocks and disk usage after a recovery on some of my partitions. Upon further
investigation, the incorrect blocks are associated with my Oracle7 dbf files.
I have Oracle shutdown. The dbf file sizes are identical to the source drive
but the blocks for these dbf files are reporting as a very small percentage of
the origonal. I can then manually copy the dbf file from the source disk to
the recovered disk and it will then report identically in both size and
blocks. What is ignite doing to these database files and is there anything I
can do to fix it to properly recover their block sizes during the reocvery
build?

[Dan Hull]

I almost hate to mention it, but a newer version of Ignite is available :)

Are these Oracle files in VG00? Are you using the -A option to back up
everything in VG00?

[Al Jordan]

I've alrady tried the upgrade to a new ignite version and nothing changed. So,
I doubt another upgrade will help. My entire drive is VG00 and I'm using the
-A option to backup the entire volume group. I'm now wondering if there isn't
some kind of patch for the cpio and/or pax functions of the ignite script that
might be causing this headache... Thoughts?

[Glenn Wagner_1]

While I was looking into the make_recovery command, I found that I had to
install the latest pax patch in order to keep my data from being corrupted. I
had problems getting the make_recovery to complete.
The patch that I installed is PHCO_20388 (on 10.20). I recommend installing
this patch or the latest pax patch and see what happens. I hope that this
helps.

[Al Jordan]

Thanks for the pax advise. I just manually tried pax'ing a dbf file to a tape
and back and sure enough, the block size was all screwed up. Will install the
pax patch PHC0_20388 and post my findings here...

[Al Jordan]

Thanks for the pax advise. I just manually tried pax'ing a dbf file to a tape
and back and sure enough, the block size was all screwed up. Will install the
pax patch PHC0_20388 and post my findings here...