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

The backup-my.cnf no longer preserves innodb_data_file_path?

Asked by Sean Chighizola

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

Question information

Language:
English Edit question
Status:
Open
For:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Alexey Kopytov (akopytov) said : 		#1

Hi Sean,

Thank you for the problem report. It appears to be a regression, so I created a bug report based on this question.

Can you help with this problem?

Provide an answer of your own, or ask Sean Chighizola for more information if necessary.

To post a message you must log in.