Remove dropped tables from a full backup when merging an incremental one
Bug #856400 reported by
Alexey Kopytov
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.0 |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.1 |
Fix Released
|
High
|
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
lp:~sergei.glushchenko/percona-xtrabackup/20-bug856400
- Alexey Kopytov (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 717 lines (+373/-100)3 files modifiedinnobackupex (+96/-37)
src/xtrabackup.cc (+157/-63)
test/t/bug856400.sh (+120/-0)
lp:~sergei.glushchenko/percona-xtrabackup/21-bug856400
- Alexey Kopytov (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 726 lines (+378/-102)3 files modifiedinnobackupex (+96/-37)
src/xtrabackup.cc (+162/-65)
test/t/bug856400.sh (+120/-0)
| Changed in percona-xtrabackup: | |
| status: | New → Confirmed |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #1 |
| Changed in percona-xtrabackup: | |
| importance: | Undecided → Medium |
| Changed in percona-xtrabackup: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Mike Siekkinen (9-mikes) wrote | #2 |
| tags: | added: i29835 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
A fix for this bug should also remove some metainfo files (e.g. xtrabackup_