new InnoDB table is not included to full prepared backup from incremental
Bug #766607 reported by
Valentine Gostev
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Critical
|
Alexey Kopytov | ||
1.6 |
Fix Released
|
Critical
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
Critical
|
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
lp:~akopytov/percona-xtrabackup/bug766607
- Stewart Smith (community): Approve
-
Diff: 466 lines (+211/-69)7 files modifiedtest/inc/common.sh (+23/-3)
test/inc/incremental_sample-db/incremental_sample-schema.sql (+0/-35)
test/run.sh (+43/-9)
test/t/bug766607.sh (+51/-0)
test/t/xb_defaults_file.sh (+25/-0)
test/t/xb_stats.sh (+2/-5)
xtrabackup.c (+67/-17)
lp:~stewart/percona-xtrabackup/bug766607-1.6
- Alexey Kopytov (community): Approve
-
Diff: 287 lines (+131/-53)4 files modifiedtest/inc/incremental_sample-db/incremental_sample-schema.sql (+0/-35)
test/run.sh (+14/-1)
test/t/bug766607.sh (+51/-0)
xtrabackup.c (+66/-17)
Changed in percona-xtrabackup: | |
milestone: | none → 1.7 |
assignee: | nobody → Valentine Gostev (core-longbow) |
importance: | Undecided → High |
Changed in percona-xtrabackup: | |
importance: | High → Critical |
Changed in percona-xtrabackup: | |
status: | Triaged → Fix Committed |
Changed in percona-xtrabackup: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Valentine,
Do you have repeatable case ?
As I understand XtraBackup should handle such case.