RE: Recover Logical Logs (the hard way)
Thanks to all who replied.
We have decided to restore to Friday's backup and try to recreate
Monday's transactions the old fashioned way. Spending time trying to
recover the logs, and then waiting for them to roll forward isn't going
to be feasible.
And yes, Art, we did catch him, but he's already out on bail...
-----Original Message-----
From: Art S. Kagel [SMTP:kagel@bloomberg.net]
Sent: Tuesday, December 15, 1998 1:55 PM
To: Scott Black
Subject: Re: Recover Logical Logs (the hard way)
Scott Black wrote:
>
> I'm running HP-UX 10.20
> Online 7.3
>
> We had a vandal come in and physically smash some of our
server's disk
> drives (before the nightly backup). The root dbspace drive is
toast.
> However the logical log drive is in good working order.
Here's the
> question:
>
> How can I save the logical log information so that when we get
back up
> and running, and restore from Friday's backup, we will be able
to roll
> forward the logs?
>
> Any hair brained scheme will be appreciated. Thanks in
advance.
If your logs were not being backed up constantly, or at least
periodically, I do not see how you can recover beyond the last
backed
up logfiles, if any. You may be toasted.
Can you recreate the missing data?
Is there any chance of recovering the reserved pages? Even
manually,
like from an oncheck dump or a dd off a partially damaged drive?
Then
you may be able to create a dummy instance that thinks the
original log
files are valid and is willing to archive them with ontape -a.
If you
know what to look for it should be possible, though tedius, with
a
binary editor, to patch up the logfile pages with the original
values
if you can get some clue as to what they were. You need the
dbspace
pages (4&5 and any additional pages linked to them if the
logspace is
not on the first page), the chunk pages (6&7 and any additional
pages
linked to them if the logspace chunks do not live on the first
page),
and the log pages.
I hope you caught this dude.
Art S. Kagel