Make xtrabackup check tables for corruption during prepare
Bug #673071 reported by
Baron Schwartz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Wishlist
|
Unassigned | ||
| 2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 2.1 |
Triaged
|
Wishlist
|
Unassigned | ||
| 2.2 |
Triaged
|
Wishlist
|
Unassigned | ||
| 2.3 |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
This is copied from an email thread on <email address hidden>:
Because there is no such thing as "too paranoid" for a backup tool, I
think that we should add an option to xtrabackup to be used with
--prepare. This option would start InnoDB and do a full scan of every
index in the whole database, checking for corruption. It should be
called --validate or --check-
Maybe we can just look at the ha_innodb.c code and see what CHECK
TABLES does, and mimic that.
| Changed in percona-xtrabackup: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Alexey Kopytov (akopytov) |
Revision history for this message
| Stewart Smith (stewart) wrote | #1 |
| Changed in percona-xtrabackup: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #2 |
| Changed in percona-xtrabackup: | |
| assignee: | Alexey Kopytov (akopytov) → nobody |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Alexey, is this at all on your radar?