I
I
Ilya Evseev2014-11-17 21:45:15
MySQL
Ilya Evseev, 2014-11-17 21:45:15

What is the cause of the error when running innobackupex --apply-log?

I have Percona SQL Server 5.6.21
I create a database backup:

innobackupex --no-timestamp /tmp/sqlbackup/
innobackupex --apply-log /tmp/sqlbackup/

The backup is created, both times innobackupex writes "completed OK!", but in the second call, the first run of "xtrabackup --prepare" displays the following warning:

...
InnoDB: The log sequence numbers 272546317 and 272546317 in ibdata files do not match the log sequence number 272548238 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.21 started; log sequence number 272548238
[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 272553181
141112 11:59:46 innobackupex: Restarting xtrabackup with command: xtrabackup ... --prepare ...
...

Restarting xtrabackup works without errors.
Question: what caused it, how serious, can it be avoided, and how exactly?

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question