Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
Re: determine needed logbackup (was: crash during log recovery)
From: Raimund Jacob (Raimund.Jacobpinuts.de)
Date: Fri Feb 18 2005 - 04:03:43 CST
Brunzema, Martin wrote:
>>>happens on the live system.
>>now it happened on the live system :(
> What happended? The error you found affects only recovery.
> So did you recover your live system and get the same error?
my initial report was for my backup/recovery playground. what i meant
today is that the live backup/recovery system is affected (the one at
the customer's site).
> the easiest way to get the information which data/logbackups you need
> is to use
> backup_history_list -r last
> If you issue this command on the live-system then it may occur that
> no logbackups are needed, because all relevant logentries are found
> on the logvolume.
> If you copy the file dbm.knl and dbm.mdf to your shadow, then the
> command should work properly on the shadow.
> Your're right that the information given by db_restartinfo is needed to
> determine which logbackups are needed:
> "Used LOG Page" is the LogIOSequence, which defines the first logpage needed
> to restart.
> "First LOG Page" is the first LogIOSequence found on the LogVolume. For your
> shadow this should be 2147483647 - which is a special value for invalid.
> Another way is not to use db_restartinfo, but parse the backup-history
> in dbm.knl. There are also all informations found (Savepoint-iosequence of the
> backup and the the range of iosequences which are contained in the logbackups.
okay, thank your for this information. i'll look into such a script next
Pinuts media+science GmbH http://www.pinuts.de
Raimund Jacob Raimund.Jacobpinuts.de
Krausenstr. 9-10 voice : +49 30 59 00 90 322
10117 Berlin fax : +49 30 59 00 90 390
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb