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 on 2012-04-17

This bug affects 2 people

	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