# log sequence number \[...\] is in the future!
**URL:** https://forums.percona.com/t/log-sequence-number-is-in-the-future/3742
**Category:** Percona XtraBackup
**Created:** [September 16, 2014, 8:06am UTC](https://forums.percona.com/t/log-sequence-number-is-in-the-future/3742 "2014-09-16T08:06:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@brsysadmin](https://forums.percona.com/u/brsysadmin)
#### Post date: [September 16, 2014, 8:06am UTC](https://forums.percona.com/t/log-sequence-number-is-in-the-future/3742/1 "2014-09-16T08:06:01Z")
Hello,
I try to use xtrabackup to create incremental backups on a test database.
Backups work with this commands :
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp /root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp --incremental /root/work/backup/backup/16092014\_150711\_INCR --incremental-basedir=/root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp --incremental /root/work/backup/backup/16092014\_150754\_INCR --incremental-basedir=/root/work/backup/backup/16092014\_150711\_INCR
But I get an error in the preparation :
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log --redo-only /root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log --redo-only /root/work/backup/backup/16092014\_150617\_FULL --incremental-dir=/root/work/backup/backup/16092014\_150711\_INCR
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log --redo-only /root/work/backup/backup/16092014\_150617\_FULL --incremental-dir=/root/work/backup/backup/16092014\_150754\_INCR
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log /root/work/backup/backup/16092014\_150617\_FULL
[…]
[COLOR=#FF0000]2014-09-16 15:16:15 7f1bcf402720 InnoDB: Error: page 0 log sequence number 468352328
InnoDB: is in the future! Current system log sequence number 468343925.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html](http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html)
InnoDB: for more information. […]
I have exactly the same error if I do :
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp /root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp --incremental /root/work/backup/backup/16092014\_150711\_INCR --incremental-basedir=/root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --no-lock --no-timestamp --incremental /root/work/backup/backup/16092014\_150754\_INCR --incremental-basedir=/root/work/backup/backup/16092014\_150711\_INCR
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log --redo-only /root/work/backup/backup/16092014\_150617\_FULL
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log --redo-only /root/work/backup/backup/16092014\_150617\_FULL --incremental-dir=/root/work/backup/backup/16092014\_150711\_INCR
# innobackupex --user=backup --password=backup\_password --use-memory=512M --apply-log /root/work/backup/backup/16092014\_150617\_FULL --incremental-dir=/root/work/backup/backup/16092014\_150754\_INCR
Did I forget a setting ? Does my backup is ok ?
Thank you in advance.
---
### Author:  [@scott.nemes](https://forums.percona.com/u/scott.nemes)
#### Post date: [September 16, 2014, 9:58am UTC](https://forums.percona.com/t/log-sequence-number-is-in-the-future/3742/2 "2014-09-16T09:58:29Z")
Hi brsysadmin
For future reference, Percona has a good guide for this here:
[url][Percona XtraBackup](http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/incremental_backups_innobackupex.html%5B/url%5D)
Basic steps:
1. Prepare the full backup (redo-only)
2. Prepare the 1st incremental backup (redo-only)
3. Prepare the 2nd incremental backup (normal; no redo-only)
4. Prepare the full backup one last time (normal; no redo-only)
So I believe your first attempt was the closest; just remove the redo-only flag from the second incremental preparation, and then it _should_ work. =)
-Scott
---
### Author:  [@brsysadmin](https://forums.percona.com/u/brsysadmin)
#### Post date: [September 17, 2014, 8:19am UTC](https://forums.percona.com/t/log-sequence-number-is-in-the-future/3742/3 "2014-09-17T08:19:56Z")
Hello,
I tried following this documentation and that’s ok.
However, when I prepare the first full backup, I get this message :
# innobackupex --use-memory=512M --apply-log --redo-only /root/work/backup/backup/17092014\_154041\_FULL
[…]
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 369628192 and 369628192 in ibdata files do not match the log sequence number 369628202 in the ib\_logfiles!
InnoDB: Database was not shutdown normally!
[…]
Is this normal ?