innodb_data_file_path is not written to backup-my.cnf

Reported by Alexey Kopytov on 2012-04-17
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
High
Sergei Glushchenko
1.6
High
Sergei Glushchenko
2.0
High
Sergei Glushchenko
2.1
High
Sergei Glushchenko

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

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
Alexey Kopytov (akopytov) wrote :

Correction: the regression in 1.6 was introduced in 1.6.6.

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

Duplicates of this bug

Other bug subscribers

Related questions