Percona XtraBackup moved to https://jira.percona.com/projects/PXB

innodb_data_file_path is not written to backup-my.cnf

Bug #983685 reported by Alexey Kopytov
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
High
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1-pre-initial-release
1.6
Fix Released
High
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 1.6.7
2.0
Fix Released
High
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.0.1
2.1
Fix Released
High
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1-pre-initial-release

Bug Description

While testing Xtrabackup 2.0, I identified the backup-my.cnf no longer records the innodb_data_file_path information. Isn't this necessary to restore a backup? Is this expected behavior or a bug? If it's expected, for my edification, why is this?

The following shows the different backup-my.cnf files for v1.6.5 and v2.0.0:

V1.6.5
# The MySQL server
[mysqld]
datadir=/mnt/hot_backup/new
innodb_data_home_dir=/mnt/hot_backup/new
innodb_log_files_in_group=3
innodb_data_file_path=ibdata1:2000M:autoextend
innodb_log_group_home_dir=/mnt/hot_backup/new
innodb_log_file_size=524288000

v2.0.0
# The MySQL server
[mysqld]
datadir=/mnt/hot_backup/new
innodb_data_home_dir=/mnt/hot_backup/new
innodb_log_files_in_group=3
innodb_log_file_size=524288000
innodb_fast_checksum=0
innodb_page_size=16384
innodb_log_block_size=512

Thanks,
Sean

Related branches

lp:~sergei.glushchenko/percona-xtrabackup/bug983685-xb1.6
Alexey Kopytov (community): Approve
Diff: 54 lines (+31/-1)
2 files modified
innobackupex (+3/-1)
test/t/bug983685.sh (+28/-0)
lp:~sergei.glushchenko/percona-xtrabackup/bug983685-xb2.0
Alexey Kopytov (community): Approve
Diff: 54 lines (+31/-1)
2 files modified
innobackupex (+3/-1)
test/t/bug983685.sh (+28/-0)
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Thank you for the bug report. It's a regression introduced in 1.6.5 and 2.0.0 by the fix for bug #733651.

Changed in percona-xtrabackup:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Correction: the regression in 1.6 was introduced in 1.6.6.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.