Bug #62587 Mysqlbackup incremental, error applying log

• Submitted: 30 Sep 2011 12:40
• Modified: 11 Dec 2011 17:33
• Reporter: Adrian Chapela Cordeiro
• Status: No Feedback
• Category: MySQL Enterprise Backup
• Severity: S2 (Serious)
• Version: 3.6.0
• OS: Linux
• CPU Architecture: Any

[30 Sep 2011 12:40] Adrian Chapela Cordeiro

Description:
I am testing the mysqlbackup utility.

I could do a full backup succesfully but when I am trying to do a incremental backup, I could do a the backup but I can't to aply to the full backup.

I am receiving error:
10930 14:24:12InnoDB: Doing recovery: scanned up to log sequence number 72837824467456
InnoDB: Doing recovery: scanned up to log sequence number 72837829710336
InnoDB: Doing recovery: scanned up to log sequence number 72837834953216
InnoDB: Doing recovery: scanned up to log sequence number 72837840196096
InnoDB: Doing recovery: scanned up to log sequence number 72837845438976
InnoDB: Doing recovery: scanned up to log sequence number 72837850681856
InnoDB: Doing recovery: scanned up to log sequence number 72837855924736
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: InnoDB: Probable data corruption on page 860
InnoDB: Original record (compact record)
InnoDB: on that page.
InnoDB: Cannot find the dir slot for record (compact record)
InnoDB: on that page!
110930 14:24:14  InnoDB: Page dump in ascii and hex (16384 bytes

How to repeat:
Do a full backup. Aply log.
Do a incremental backup, try to aply log.

[30 Sep 2011 12:41] Adrian Chapela Cordeiro

Output error from mysqlbackup

Attachment: error_mysqlbackup (application/octet-stream, text), 50.77 KiB.

[30 Sep 2011 12:42] Adrian Chapela Cordeiro

I am testing this utility to take a decision because I am trying to do incremental backups.

[30 Sep 2011 18:02] Valeriy Kravchuk

Please, check if the same problem still happens with a newer version, 3.6.1.

[30 Sep 2011 21:04] Adrian Chapela Cordeiro

I can't get newer version from trials. Newer version available from trials is MySQL Backup 3.6.0

[11 Nov 2011 17:33] Sveta Smirnova

Thank you for the report.

Please send output of commands you use to call mysqlbackup when doing full backup, incremental backup, then restore.

[12 Dec 2011 7:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".