hello list!
my standby-scenario is not quite working as expected (7.5.0.26 on
linux). it works like this:
- full backup every 24h
- autolog enabled
- explicit log backup every hour (rsync all fragments to standby system)
- recovery of log backups every hour
the log recovery looks like this: identify the last log fragment that
was successfully imported (from backup history). recover_start that
fragment, then recover_replace all the remaining fragments, then
recover_cancel.
after setting up, this works quite well for some days but then it starts
failing: the recover_start returns -7075. i tried starting with
earlier/later fragments, but they all return -7075.
the db_restartinfo of the standby instance looks like this:
Used LOG Page 0
First LOG Page 2147483647
Restartable 1
Id Restart Record XXX
Id LOG Info
Consistent 1
my questions are: isn't this supposed to work? why doesn't it? has it
anything to do with the nightly full backup? does that disturb the
order/content of the log fragments?
perhaps it's the mix of automatic and explicit log backups? in my first
attempt i worked with explicit log backups only, which triggered 2 bugs
in the kernel (the latter of which is not fixed yet, afaik).
any hint is appreciated,
Raimund
--
Die Lösung zum effizienten eCRM und eMail-Marketing, mehr unter
Pinuts Universal Messenger http://www.pinuts.de/universalmessenger/
Pinuts media+science GmbH http://www.pinuts.de
Dipl.-Inform. Raimund Jacob [EMAIL PROTECTED]
Krausenstr. 9-10 voice : +49 30 59 00 90 322
10117 Berlin fax : +49 30 59 00 90 390
Germany
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
