Bug #59910 Server crashes when logs are applied for incremental backup before full backup
Submitted: 2 Feb 2011 23:28 Modified: 12 Oct 2011 18:38
Reporter: Hema Sridharan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:MEB 3.6 OS:Linux
Assigned to: Thava Alagu CPU Architecture:Any

[2 Feb 2011 23:28] Hema Sridharan 
Description:
Create databases, tables, load data.
Execute MEB
Add some more data in tables
Execute incremental backup
Now stop server and then apply log for incremental backup without applying for full backup.
Server crashes.

110203  2:01:40  InnoDB: Assertion failure in thread 1106364736 in file btr/btr0pcur.c line 402
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_frame_get_page_no(page)

How to repeat:
Please find the attached test case to reproduce the bug. I have also attached the crash dump
[2 Feb 2011 23:28] Hema Sridharan 
The test file to reproduce the failure

Attachment: increment_crash.test (application/octet-stream, text), 2.79 KiB.
[2 Feb 2011 23:29] Hema Sridharan 
The crash dump

Attachment: crash (application/octet-stream, text), 39.59 KiB.
[4 Feb 2011 11:53] Thava Alagu 
This seems to be a non-bug. Following order is required to use incremental backup:
   1. Do full backup.
   2. Run apply-log on full-backup.
   3. Create some tables and add data, then take incremental backup.
   [ Step 2 and 3 can be in any order ]
   4. Run apply-incremental-backup operation to apply incremental backup
      on full backup. [ Prior to 3.6, this operation was called 
      --apply-log --incremental ].

There are 2 important things to note:
   (1) The step-2 in above is required. i.e. You should run apply-log on
       full backup before considering applying the incremental backup.
   (2) you should not run, --apply-log on incremental backup itself. 
       The destination repository for apply-log is always full-backup.

Please clarify if the above procedures were followed. Also, if you think the documentation for above is not clear, we should fix it accordingly.
[14 Feb 2011 10:59] Valeriy Kravchuk 
Also I wonder what server version you were working with.
[14 Feb 2011 16:03] Hema Sridharan 
Valeriy, I am using mysql-5.1 server (i.e mysql-5.1-meb tree)
[12 Oct 2011 18:38] Sveta Smirnova 
Fixed in version 3.6.0