Innobackupex doesn't add file-per-table setting for table-independent backups

Bug #930062 reported by Matt on 2012-02-10
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

When using the --export option for innobackupex to create table-independent InnoDB backups the auto-generated backup-my.cnf file doesn't contain the option "innodb-file-per-table=1". This means if you copy the backup to a different server for preparation and use the backup-my.cnf file as the defaults file for innobackupex, it fails complaining that file_per_table isn't enabled.

Version info:

$ innobackupex --version
InnoDB Backup Utility v1.5.1-xtrabackup;

$ xtrabackup --version
xtrabackup version 1.6.4 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: 314)

$ mysql --version
mysql Ver 14.14 Distrib 5.5.14, for Linux (x86_64) using readline 5.1

$ uname -a
Linux ***** 2.6.18-194.32.1.el5 #1 SMP Mon Dec 20 10:52:42 EST 2010 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

Related branches

Matt (whereswardy) wrote :

I've noticed that xtrabackup itself has a command line option --file-per-table to tell it that it's dealing with this option during the backup, but there's no way to set this if you're using innobackupex. Perhaps innobackupex should always set this option with xtrabackup if using --export?

Stewart Smith (stewart) on 2012-06-15
Changed in percona-xtrabackup:
importance: Undecided → High
Changed in percona-xtrabackup:
importance: High → Medium
Ovais Tariq (ovais-tariq) wrote :

Is there any chance that this bug could be fixed in the next release?

tags: added: i29680

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers