stale xtrabackup_tmp* files after applying incremental backups

Bug #1079135 reported by Alexey Kopytov on 2012-11-15
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Sergei Glushchenko
Sergei Glushchenko
Sergei Glushchenko

Bug Description

The fix for bug #932623 handles table rotation between full and incremental backups by comparing space IDs in the full backup directory and delta files having the same names. On space ID mismatch, the old table in the full backup directory is renamed to xtrabackup_tmp_OLDID.ibd. We need this to handle cases when, for example, between full and incremental backups table t1 is renamed to t2, and t2 is renamed to t1. When applying to (the old) t1.ibd, we cannot simply remove t1.ibd, as it will be renamed to t2.ibd later, when applying t2.ibd.

However, in cases when a table is simply recreated with a new ID (rather than renamed), the old t1 is renamed to xtrabackup_tmp_OLDID.ibd, and a new t1 is created from, but xtrabackup_tmp_OLDID.ibd is left in the full backup directory.

Related branches

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

Other bug subscribers