Remove dropped tables from a full backup when merging an incremental one

Bug #856400 reported by Alexey Kopytov on 2011-09-22
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Sergei Glushchenko
Sergei Glushchenko
Sergei Glushchenko

Bug Description

This is a counterpart of bug #759701.

Tables that were dropped between taking a full backup and an incremental one are present in the full backup directory, and are not removed when merging an incremental one which does not have them. This applies to .frm files and both non-InnoDB tables and InnoDB per-table tablespaces, even though InnoDB tables are removed from the data dictionary when applying deltas to the system tablespace. Which leads to orphaned frms and tables after restore.

So innobackupex should be fixed to remove files corresponding to tables that are missing in the incremental backup directory.

Related branches

Alexey Kopytov (community): Approve on 2013-04-24
George Ormond Lorch III: Approve (g2) on 2013-03-13
Alexey Kopytov (community): Approve on 2013-04-24
George Ormond Lorch III: Approve (g2) on 2013-03-13
Changed in percona-xtrabackup:
status: New → Confirmed
Alexey Kopytov (akopytov) wrote :

A fix for this bug should also remove some metainfo files (e.g. xtrabackup_slave_info) if they are not present in the incremental backup.

Stewart Smith (stewart) on 2012-02-07
Changed in percona-xtrabackup:
importance: Undecided → Medium
Stewart Smith (stewart) on 2012-06-15
Changed in percona-xtrabackup:
status: Confirmed → Triaged
Mike Siekkinen (9-mikes) wrote :

This also seems to apply to partitions that are dropped betwween incrementals.

Jervin R (revin) on 2013-02-27
tags: added: i29835
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions