Not the answer you need?
Register and ask your own question!

innobackupex --apply-logs fail with checksum mismatch in data file ./ibdata1

haruglory007haruglory007 EntrantCurrent User Role Beginner
Using Percona Xtrabackup Version 2.3.3
Getting this error when doing --apply-logs:

Where should I start to look into debugging this error?
root@backup:/srv/db-backups/# innobackupex --apply-log /srv/db-backups/ --defaults-file=/srv/db-backups/backup-my.cnf --ibbackup=xtrabackup --use-memory=4G

170612 14:41:29 innobackupex: Starting the apply-log operation




IMPORTANT: Please check that the apply-log run completes successfully.

At the end of a successful apply-log run innobackupex

prints "completed OK!".




innobackupex version 2.3.3 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 525ca7d)

xtrabackup: cd to /srv/db-backups/admin/

xtrabackup: This target seems to be not prepared yet.

xtrabackup: xtrabackup_logfile detected: size=4210688, start_lsn=(3318033660)

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 1

xtrabackup: innodb_log_file_size = 4210688

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 1

xtrabackup: innodb_log_file_size = 4210688

xtrabackup: Starting InnoDB instance for recovery.

xtrabackup: Using 4294967296 bytes for buffer pool (set by --use-memory parameter)

InnoDB: Using atomics to ref count buffer pool pages

InnoDB: The InnoDB memory heap is disabled

InnoDB: Mutexes and rw_locks use GCC atomic builtins

InnoDB: Memory barrier is not used

InnoDB: Compressed tables use zlib 1.2.8

InnoDB: Using CPU crc32 instructions

InnoDB: Initializing buffer pool, size = 4.0G

InnoDB: Completed initialization of buffer pool

InnoDB: Restoring page 0 of tablespace 0

InnoDB: Doublewrite does not have page_no=0 of space: 0

InnoDB: checksum mismatch in data file ./ibdata1

InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!

xtrabackup: innodb_init(): Error occured.

My backup-my.cnf looks like this:
# This MySQL options file was generated by innobackupex.

# The MySQL server

[mysqld]

innodb_checksum_algorithm=innodb

innodb_log_checksum_algorithm=innodb

innodb_data_file_path=ibdata1:10M:autoextend

innodb_log_files_in_group=2

innodb_log_file_size=2147483648

innodb_fast_checksum=true

innodb_page_size=16384

innodb_log_block_size=512

innodb_undo_directory=.

innodb_undo_tablespaces=0
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.