Mysql热备增量备份与恢复（三）--全备+增量1恢复
1 对于全备的恢复
[mysql@server ~]$ innobackupex --no-timestamp --defaults-file=/etc/my.cnf --apply-log --redo-only /home/mysql/db_full_20141103/
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p
141113 18:35:47 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!".
141113 18:35:47 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/home/mysql/db_full_20141103/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/home/mysql/db_full_20141103 --apply-log-only
xtrabackup version 2.2.6 based on MySQL server 5.6.21 Linux (x86_64) (revision id: )
xtrabackup: cd to /home/mysql/db_full_20141103
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(2081824)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 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.3
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure you are using the right ib_logfiles to start up the database. Log sequence number in the ib_logfiles is 2081824, logsequence numbers stamped to ibdata file headers are between 2117907 and 2117907.
InnoDB: The log sequence numbers 2117907 and 2117907 in ibdata files do not match the log sequence number 2081824 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...
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 301 log sequence number 2082176
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 306 log sequence number 2082546
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 307 log sequence number 2082875
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 308 log sequence number 2083241
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 309 log sequence number 2083607
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 310 log sequence number 2083981
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 311 log sequence number 2084498
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 312 log sequence number 2084823
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 313 log sequence number 2085177
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 314 log sequence number 2085579
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 315 log sequence number 2085937
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 316 log sequence number 2086258
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 317 log sequence number 2086628
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 318 log sequence number 2087006
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 319 log sequence number 2087388
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 320 log sequence number 2087738
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 321 log sequence number 2088140
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 322 log sequence number 2088494
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 323 log sequence number 2088844
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 324 log sequence number 2089169
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 326 log sequence number 2089567
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 327 log sequence number 2089925
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 328 log sequence number 2090254
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 329 log sequence number 2090595
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 330 log sequence number 2090929
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 331 log sequence number 2091266
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 332 log sequence number 2091644
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 333 log sequence number 2091982
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 334 log sequence number 2092319
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 335 log sequence number 2092701
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 336 log sequence number 2093103
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 337 log sequence number 2093453
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 338 log sequence number 2093839
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 339 log sequence number 2094213
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 340 log sequence number 2094534
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 341 log sequence number 2094896
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 342 log sequence number 2095286
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 343 log sequence number 2095599
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 344 log sequence number 2095953
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 345 log sequence number 2096323
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 346 log sequence number 2096668
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 347 log sequence number 2096985
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 348 log sequence number 2097383
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 349 log sequence number 2097765
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 350 log sequence number 2098074
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 351 log sequence number 2098468
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 352 log sequence number 2098826
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 353 log sequence number 2099156
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 354 log sequence number 2099554
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 355 log sequence number 2099887
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 356 log sequence number 2100281
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 357 log sequence number 2100602
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 358 log sequence number 2100927
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 359 log sequence number 2101301
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 360 log sequence number 2101618
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 361 log sequence number 2101968
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 362 log sequence number 2102297
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 363 log sequence number 2102659
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 364 log sequence number 2103009
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 365 log sequence number 2103338
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 366 log sequence number 2103680
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 367 log sequence number 2104030
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 368 log sequence number 2104432
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 369 log sequence number 2104810
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 370 log sequence number 2105160
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 371 log sequence number 2105550
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 372 log sequence number 2105933
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 373 log sequence number 2106243
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 374 log sequence number 2106618
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 375 log sequence number 2107017
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 376 log sequence number 2107347
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 377 log sequence number 2107730
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 378 log sequence number 2108068
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 379 log sequence number 2108378
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 380 log sequence number 2108749
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 381 log sequence number 2109132
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 382 log sequence number 2109507
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 383 log sequence number 2109878
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 384 log sequence number 2110269
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 385 log sequence number 2110624
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 386 log sequence number 2111023
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 387 log sequence number 2111345
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 388 log sequence number 2111732
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 389 log sequence number 2112131
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 390 log sequence number 2112466
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 391 log sequence number 2112845
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 392 log sequence number 2113220
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 393 log sequence number 2113599
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 394 log sequence number 2113982
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 395 log sequence number 2114353
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 396 log sequence number 2114687
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 397 log sequence number 2115034
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 398 log sequence number 2115437
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 399 log sequence number 2115808
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 400 log sequence number 2116167
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 401 log sequence number 2116477
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 402 log sequence number 2116819
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 403 log sequence number 2117218
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 404 log sequence number 2117573
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 405 log sequence number 2117907
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
InnoDB: Last MySQL binlog file position 0 24875, file name ./mybinlog.000002
2014-11-13 18:35:48 2ac036ab5670 InnoDB: Error: page 0 log sequence number 2084295
InnoDB: is in the future! Current system log sequence number 2081824.
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
InnoDB: for more information.
[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 24875, file name ./mybinlog.000002
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 2081824
141113 18:35:48 innobackupex: completed OK!
2 增量1恢复
[mysql@server ~]$ innobackupex --no-timestamp --defaults-file=/etc/my.cnf --apply-log --redo-only /home/mysql/db_full_20141103/ --incremental-dir=/home/mysql/db_full_20141113-incr1
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p
141113 18:36:31 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!".
141113 18:36:31 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/home/mysql/db_full_20141103/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/home/mysql/db_full_20141103 --apply-log-only --incremental-dir=/home/mysql/db_full_20141113-incr1
xtrabackup version 2.2.6 based on MySQL server 5.6.21 Linux (x86_64) (revision id: )
incremental backup from 2081824 is enabled.
xtrabackup: cd to /home/mysql/db_full_20141103
xtrabackup: This target seems to be already prepared.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(2117817)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend
xtrabackup: innodb_log_group_home_dir = /home/mysql/db_full_20141113-incr1
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /home/mysql/db_full_20141113-incr1/ibdata1.delta is 16384 bytes
Applying /home/mysql/db_full_20141113-incr1/ibdata1.delta to ./ibdata1...
xtrabackup: page size for /home/mysql/db_full_20141113-incr1/dao/t_dao.ibd.delta is 16384 bytes
Applying /home/mysql/db_full_20141113-incr1/dao/t_dao.ibd.delta to ./dao/t_dao.ibd...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend
xtrabackup: innodb_log_group_home_dir = /home/mysql/db_full_20141113-incr1
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 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.3
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 2081824 and 2081824 in ibdata files do not match the log sequence number 2117817 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: Last MySQL binlog file position 0 24907, file name ./mybinlog.000001
[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 24907, file name ./mybinlog.000001
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 2117817
innobackupex: Starting to copy non-InnoDB files in '/home/mysql/db_full_20141113-incr1'
innobackupex: to the full backup directory '/home/mysql/db_full_20141103'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/xtrabackup_info' to '/home/mysql/db_full_20141103/xtrabackup_info'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/xtrabackup_binlog_info' to '/home/mysql/db_full_20141103/xtrabackup_binlog_info'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/host.MYI' to '/home/mysql/db_full_20141103/mysql/host.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition_type.MYI' to '/home/mysql/db_full_20141103/mysql/time_zone_transition_type.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/plugin.MYI' to '/home/mysql/db_full_20141103/mysql/plugin.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/slow_log.CSM' to '/home/mysql/db_full_20141103/mysql/slow_log.CSM'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_keyword.MYI' to '/home/mysql/db_full_20141103/mysql/help_keyword.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition.frm' to '/home/mysql/db_full_20141103/mysql/time_zone_transition.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/servers.frm' to '/home/mysql/db_full_20141103/mysql/servers.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/columns_priv.frm' to '/home/mysql/db_full_20141103/mysql/columns_priv.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/columns_priv.MYD' to '/home/mysql/db_full_20141103/mysql/columns_priv.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/func.MYD' to '/home/mysql/db_full_20141103/mysql/func.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/event.MYD' to '/home/mysql/db_full_20141103/mysql/event.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proc.frm' to '/home/mysql/db_full_20141103/mysql/proc.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/tables_priv.frm' to '/home/mysql/db_full_20141103/mysql/tables_priv.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_relation.frm' to '/home/mysql/db_full_20141103/mysql/help_relation.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/event.frm' to '/home/mysql/db_full_20141103/mysql/event.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/user.MYI' to '/home/mysql/db_full_20141103/mysql/user.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_leap_second.MYD' to '/home/mysql/db_full_20141103/mysql/time_zone_leap_second.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition_type.MYD' to '/home/mysql/db_full_20141103/mysql/time_zone_transition_type.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proc.MYD' to '/home/mysql/db_full_20141103/mysql/proc.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/procs_priv.MYD' to '/home/mysql/db_full_20141103/mysql/procs_priv.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/slow_log.frm' to '/home/mysql/db_full_20141103/mysql/slow_log.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proxies_priv.frm' to '/home/mysql/db_full_20141103/mysql/proxies_priv.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/servers.MYD' to '/home/mysql/db_full_20141103/mysql/servers.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_name.MYD' to '/home/mysql/db_full_20141103/mysql/time_zone_name.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/plugin.MYD' to '/home/mysql/db_full_20141103/mysql/plugin.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proxies_priv.MYI' to '/home/mysql/db_full_20141103/mysql/proxies_priv.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_relation.MYD' to '/home/mysql/db_full_20141103/mysql/help_relation.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_category.MYD' to '/home/mysql/db_full_20141103/mysql/help_category.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone.MYD' to '/home/mysql/db_full_20141103/mysql/time_zone.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/plugin.frm' to '/home/mysql/db_full_20141103/mysql/plugin.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/ndb_binlog_index.MYD' to '/home/mysql/db_full_20141103/mysql/ndb_binlog_index.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/general_log.frm' to '/home/mysql/db_full_20141103/mysql/general_log.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone.MYI' to '/home/mysql/db_full_20141103/mysql/time_zone.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_topic.MYD' to '/home/mysql/db_full_20141103/mysql/help_topic.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/procs_priv.MYI' to '/home/mysql/db_full_20141103/mysql/procs_priv.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_category.frm' to '/home/mysql/db_full_20141103/mysql/help_category.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/func.frm' to '/home/mysql/db_full_20141103/mysql/func.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition.MYD' to '/home/mysql/db_full_20141103/mysql/time_zone_transition.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_name.frm' to '/home/mysql/db_full_20141103/mysql/time_zone_name.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/general_log.CSV' to '/home/mysql/db_full_20141103/mysql/general_log.CSV'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition_type.frm' to '/home/mysql/db_full_20141103/mysql/time_zone_transition_type.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/slow_log.CSV' to '/home/mysql/db_full_20141103/mysql/slow_log.CSV'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/host.frm' to '/home/mysql/db_full_20141103/mysql/host.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_leap_second.MYI' to '/home/mysql/db_full_20141103/mysql/time_zone_leap_second.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/db.MYI' to '/home/mysql/db_full_20141103/mysql/db.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/columns_priv.MYI' to '/home/mysql/db_full_20141103/mysql/columns_priv.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/tables_priv.MYI' to '/home/mysql/db_full_20141103/mysql/tables_priv.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_leap_second.frm' to '/home/mysql/db_full_20141103/mysql/time_zone_leap_second.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/servers.MYI' to '/home/mysql/db_full_20141103/mysql/servers.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/general_log.CSM' to '/home/mysql/db_full_20141103/mysql/general_log.CSM'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/ndb_binlog_index.MYI' to '/home/mysql/db_full_20141103/mysql/ndb_binlog_index.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_keyword.frm' to '/home/mysql/db_full_20141103/mysql/help_keyword.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/host.MYD' to '/home/mysql/db_full_20141103/mysql/host.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/db.MYD' to '/home/mysql/db_full_20141103/mysql/db.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone.frm' to '/home/mysql/db_full_20141103/mysql/time_zone.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_keyword.MYD' to '/home/mysql/db_full_20141103/mysql/help_keyword.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proc.MYI' to '/home/mysql/db_full_20141103/mysql/proc.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/event.MYI' to '/home/mysql/db_full_20141103/mysql/event.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/func.MYI' to '/home/mysql/db_full_20141103/mysql/func.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/tables_priv.MYD' to '/home/mysql/db_full_20141103/mysql/tables_priv.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_topic.frm' to '/home/mysql/db_full_20141103/mysql/help_topic.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_category.MYI' to '/home/mysql/db_full_20141103/mysql/help_category.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/ndb_binlog_index.frm' to '/home/mysql/db_full_20141103/mysql/ndb_binlog_index.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/user.frm' to '/home/mysql/db_full_20141103/mysql/user.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_name.MYI' to '/home/mysql/db_full_20141103/mysql/time_zone_name.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_topic.MYI' to '/home/mysql/db_full_20141103/mysql/help_topic.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/time_zone_transition.MYI' to '/home/mysql/db_full_20141103/mysql/time_zone_transition.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/proxies_priv.MYD' to '/home/mysql/db_full_20141103/mysql/proxies_priv.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/db.frm' to '/home/mysql/db_full_20141103/mysql/db.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/user.MYD' to '/home/mysql/db_full_20141103/mysql/user.MYD'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/procs_priv.frm' to '/home/mysql/db_full_20141103/mysql/procs_priv.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/mysql/help_relation.MYI' to '/home/mysql/db_full_20141103/mysql/help_relation.MYI'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/dao/t_dao.frm' to '/home/mysql/db_full_20141103/dao/t_dao.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/dao/db.opt' to '/home/mysql/db_full_20141103/dao/db.opt'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/setup_instruments.frm' to '/home/mysql/db_full_20141103/performance_schema/setup_instruments.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/file_summary_by_instance.frm' to '/home/mysql/db_full_20141103/performance_schema/file_summary_by_instance.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_summary_global_by_event_name.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_summary_global_by_event_name.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/mutex_instances.frm' to '/home/mysql/db_full_20141103/performance_schema/mutex_instances.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/setup_consumers.frm' to '/home/mysql/db_full_20141103/performance_schema/setup_consumers.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_summary_by_thread_by_event_name.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_summary_by_thread_by_event_name.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/file_summary_by_event_name.frm' to '/home/mysql/db_full_20141103/performance_schema/file_summary_by_event_name.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/file_instances.frm' to '/home/mysql/db_full_20141103/performance_schema/file_instances.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_history_long.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_history_long.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/threads.frm' to '/home/mysql/db_full_20141103/performance_schema/threads.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/cond_instances.frm' to '/home/mysql/db_full_20141103/performance_schema/cond_instances.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/db.opt' to '/home/mysql/db_full_20141103/performance_schema/db.opt'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_summary_by_instance.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_summary_by_instance.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/rwlock_instances.frm' to '/home/mysql/db_full_20141103/performance_schema/rwlock_instances.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/performance_timers.frm' to '/home/mysql/db_full_20141103/performance_schema/performance_timers.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_history.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_history.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/setup_timers.frm' to '/home/mysql/db_full_20141103/performance_schema/setup_timers.frm'
innobackupex: Copying '/home/mysql/db_full_20141113-incr1/performance_schema/events_waits_current.frm' to '/home/mysql/db_full_20141103/performance_schema/events_waits_current.frm'
141113 18:36:32 innobackupex: completed OK!
3 比对恢复后的lsn 与增量1 的lsn
[mysql@server ~]$ cat /home/mysql/db_full_20141103/
backup-my.cnf ibdata1 performance_schema/ xtrabackup_binlog_info xtrabackup_info
dao/ mysql/ test/ xtrabackup_checkpoints xtrabackup_logfile
[mysql@server ~]$ cat /home/mysql/db_full_20141103/xtrabackup_checkpoints
backup_type = full-prepared
from_lsn = 0
to_lsn = 2117817
last_lsn = 2117817
compact = 0
[mysql@server ~]$ cat /home/mysql/db_full_20141113-incr1/xtrabackup_checkpoints
backup_type = incremental
from_lsn = 2081824
to_lsn = 2117817
last_lsn = 2117817
compact = 0
4 删除当前库
[mysql@server ~]$ rm -rf /data/mysql/dao_3306/data/*
5 恢复到当前数据库位置
[mysql@server ~]$ cp -r /home/mysql/db_full_20141103/* /data/mysql/dao_3306/data/
6 查看数据
[mysql@server ~]$ mysqld_multi start 3306
[mysql@server ~]$ mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.5.38-log MySQL Community Server (GPL)
Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
"root@localhost Thu Nov 13 18:38:58 2014 18:38:58 [(none)]>use dao
Database changed
"root@localhost Thu Nov 13 18:39:01 2014 18:39:01 [dao]>select count(*) from t_dao ;
+----------+
| count(*) |
+----------+
| 1200 |
+----------+
1 row in set (0.02 sec)
"root@localhost Thu Nov 13 18:39:06 2014 18:39:06 [dao]>exit
Bye
至此 增量一 恢复成功