Innobackupex apply-log fail

Asked by Ramil on 2016-10-04

I do backup for my servers with this two commands:

innobackupex --defaults-file=/etc/mysql/my.cnf --no-timestamp --user=... --password=... --stream=tar ./ | ssh -i ssh_key backup@backup_server "cat - | tar -C /backup/mysql -xi"

and after that:

ssh -i ssh_key backup@backup_server innobackupex --defaults-file=/backup/etc/mysql/my.cnf --ibbackup=xtrabackup --apply-log /backup/mysql

And on two my servers I got this errors on second stage:

"InnoDB: Log block 126667943 at lsn 35798981889024 has valid header, but checksum field contains 4048894271, should be 164082245
InnoDB: Doing recovery: scanned up to log sequence number 35798981889024 (8%)
InnoDB: We scanned the log up to 35798981889024. A checkpoint was at 35797549839028 and the maximum LSN on a database page was 35813680157998. It is possible that the database is now corrupt!
InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 25 row operations to undo
InnoDB: Trx id counter is 32587410688
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 InnoDB: Page [page id: space=438, page number=65281790] log sequence number 35801468155494 is in the future! Current system log sequence number 35798981889773.
InnoDB: Page [page id: space=439, page number=54493185] log sequence number 35813035535035 is in the future! Current system log sequence number 35798981889773.
InnoDB: Page [page id: space=264, page number=527660] log sequence number 35813049261708 is in the future! Current system log sequence number 35798981889773.
InnoDB: Page [page id: space=439, page number=54502754] log sequence number 35890796972444 is in the future! Current system log sequence number 3579898188977
InnoDB: Page [page id: space=439, page number=54502754] log sequence number 35890796972444 is in the future! Current system log sequence number 3579898188977
InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery."

innobackupex -v
innobackupex version 2.4.3 Linux (x86_64) (revision id: 6a46905)

Can anybody help me with this?

Question information

Language:
English Edit question
Status:
Solved
For:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB Edit question
Assignee:
No assignee Edit question
Solved by:
Ramil
Solved:
2016-10-06
Last query:
2016-10-06
Last reply:
Ramil (ingles) said : #1

if somebody interesting I update Ubuntu to 16.04 and it solve my problem. Don't have idea how.