Xtrabackup does not backup table structure in a readable format

Bug #1163857 reported by Olivier Doucet on 2013-04-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Invalid
Undecided
Unassigned

Bug Description

XtraBackup is backuping .frm files, that are not human readable.

Based on documentation, if you want to restore just one table, you have to :
1) Create the table with CREATE TABLE ...
2) Discard tablespace
3) Import tablespace

So to do step 1, you would need a readable file for the table structure (a .sql file with the CREATE TABLE statement).

Of course I can use mysqldump for this, but this is not recommended, because there could be an ALTER TABLE between my mysqldump and xtrabackup execution.

So adding an option to innobackupex to create a .sql file with the table structure just before backuping it would be really nice.
If you have another solution, please explain it in documentation more clearly here : http://www.percona.com/doc/percona-xtrabackup/xtrabackup_bin/exporting_importing_tables.html

Alexey Kopytov (akopytov) wrote :

Olivier,

We have an identical feature request reported as https://blueprints.launchpad.net/percona-xtrabackup/+spec/create-table-for-exported-tables

I'm referencing this report from the BP and closing the bug as Invalid, because LP does not provide a more appropriate status.

Changed in percona-xtrabackup:
status: New → Invalid

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1209

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

Other bug subscribers