new InnoDB table is not included to full prepared backup from incremental

Bug #766607 reported by Valentine Gostev on 2011-04-19
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

After taking a full backup, we create an InnoDB table in its own table space. If we then take incremental backup, finally prepared backup will not contain table created after full and before incremental backup.

Related branches

Changed in percona-xtrabackup:
milestone: none → 1.7
assignee: nobody → Valentine Gostev (core-longbow)
importance: Undecided → High
Vadim Tkachenko (vadim-tk) wrote :


Do you have repeatable case ?

As I understand XtraBackup should handle such case.

Valentine Gostev (longbow) wrote :

Vadim, linked branch contains test test/t/ which indicates that feature works fine, but if we run the steps from test case manually, we do not get newly created table in full backup dir after applying incremental changes.

Then we discussed and after further investigation it was found that while running test case xtrabackup calls "open("./inctest/t2.ibd", O_RDWR|O_CREAT|O_EXCL, 0664) = 11", but when the same manually "open("./inctest/t2.ibd", O_RDWR|O_CREAT|O_EXCL, 0664) = 11" is not called.

Changed in percona-xtrabackup:
status: New → Confirmed
status: Confirmed → Triaged
assignee: Valentine Gostev (core-longbow) → Alexey Kopytov (akopytov)
tags: added: incremental xtrabackup
Alexey Kopytov (akopytov) wrote :

Attaching the script which reproduces the bug. This is what I would actually like to have as a test case.

Alexey Kopytov (akopytov) wrote :

The problem is that when a new table is added after taking a full backup *and* log files have been flushed before an incremental one, the new table data goes to a .delta file. When trying to apply that .delta to a full backup later, xtrabackup_apply_delta() fails because the corresponding data file cannot be found.

The difference with the situation when log files have not been flushed before taking an incremental backup is that in this case a file creation event is in the log file, so .ibd is then created when doing crash recovery and replaying the log. The corresponding .delta file in this case will be empty.

I think the fix is to explicitly create a tablespace before applying the .delta file when the corresponding .ibd is missing.

Stewart Smith (stewart) on 2011-05-20
Changed in percona-xtrabackup:
importance: High → Critical
Changed in percona-xtrabackup:
status: Triaged → Fix Committed
Changed in percona-xtrabackup:
status: Fix Committed → Fix Released
Sachin Kale (sachin-zmanda) wrote :

I followed the steps for restoring as mentioned in link with xtrabackup 1.6.2 ubuntu platform.

The final directory which was created did not have "frm" file for the new table although the ibd file was present, so in all, the new table created after full backup was not restored completely.
Is this expected?

the backup directory had "<table>.frm", "<table>", "<table>ibd.meta" files.

Emil Goicovici (emy-cs) wrote :

I have the same problem with xtrabackup 1.6.2: the .ibd file is created (thanks to the fix made for this bug) from the ".delta" file which is present in the incremental backup, but the .frm file is missing. I had to manually copy it from the incremental backup to the MySQL data folder in order to make these tables visible again after restore.

In order to reproduce it, the scenario is the following: a full backup is performed; after this, a new InnoDB table is created in the MySQL database, followed by an incremental backup. The .delta and .meta files appear in the incremental backup as expected, but then, when performing the --apply-log step to unify the base backup with the incremental one, the .frm file is NOT copied from the incremental backup folder to the base backup folder.

Alexey Kopytov (akopytov) wrote :

The problem with .frm files is bug #759701.

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments