MySQL 5.6 fails to start on the incremental backup prepared with 2.4 and non-default innodb_data_file_path
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Fix Released
|
High
|
Sergei Glushchenko | |||
2.4 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
XtraBackup 2.4 fails to restore backups when a non-default innodb_
One full + incremental with xtrabackup 2.3 (using innobackupex) and percona server 5.6 (with innodb_
One full + incremental with xtrabackup 2.4 and percona server 5.7 (with innodb_
One full + incremental with xtrabackup 2.4 and percona server 5.6 (with default innodb_
One full + incremental with xtrabackup 2.4 and percona server 5.6 (with innodb_
2017-03-01 04:24:06 12014 [ERROR] InnoDB: Cannot create log files because data files are corrupt or not in sync with each other
2017-03-01 04:24:06 12014 [ERROR] Plugin 'InnoDB' init function returned error.
2017-03-01 04:24:06 12014 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-03-01 04:24:06 12014 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-03-01 04:24:06 12014 [ERROR] Aborting
Attached go steps to test this, and easily reproduce it. Just start one CentOS 6 vagrant VM and run the provided steps (note that it's all automated, except adding the LSN number to the incremental backup). The innodb_
Let me know if you need anything else from my side.
Agustín.
Changed in percona-xtrabackup: | |
importance: | Undecided → Critical |
Tested with MySQL 5.6 with PXB 2.4:
Result after copy-back+start:
2017-03-06 06:43:10 27284 [ERROR] InnoDB: Cannot create log files because data files are corrupt or not in sync with each other
2017-03-06 06:43:10 27284 [ERROR] Plugin 'InnoDB' init function returned error.
2017-03-06 06:43:10 27284 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-03-06 06:43:10 27284 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-03-06 06:43:10 27284 [ERROR] Aborting
Took 1 full + 2 incrementals with following my.cnf:
$ cat my.sandbox.cnf /tmp/mysql_ sandbox5635. sock
[client]
user=root
password=
port=5635
socket=
[mysqld] sandbox5635. sock .rzaev/ Percona_ Servers/ MySQLs/ 5.6.35 .rzaev/ sandboxes/ msb_5_6_ 35/data .rzaev/ sandboxes/ msb_5_6_ 35/tmp table_names = 0 .rzaev/ sandboxes/ msb_5_6_ 35/data/ mysql_sandbox56 35.pid msandbox. err data_file_ path = ibdata1: 100M;ibdata2: 10M:autoextend
user = shahriyar.rzaev
port = 5635
socket = /tmp/mysql_
basedir = /home/shahriyar
datadir = /home/shahriyar
tmpdir = /home/shahriyar
lower_case_
pid-file = /home/shahriyar
bind-address = 127.0.0.1
log-error=
innodb_