Hi,
I’m testing out Xtrabackup on my local to see how it works and I’ve followed the steps in documentation to create backups and prepare them for restore. I noticed during the prepared stage there is statement reads “log sequence number in ibdata files does not match the LSN in ib_logfiles”. If I use innobackupex for backup and restore then I don’t see the message. What does innobackupex does differently compare to xtrabackup? (other than copying MyISAM files and other files)
111016 20:12:57 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait…
111016 20:12:57 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait…
111016 20:12:57 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111016 20:12:57 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
111016 20:12:57 Percona XtraDB (http://www.percona.com) 1.0.13-12.4 started; log sequence number 5184680460
[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
111016 20:12:57 InnoDB: Starting shutdown…
111016 20:12:57 InnoDB: Shutdown completed; log sequence number 5184680460
111016 20:12:57 innobackupex-1.5.1: completed OK!
The database was able to retore properly, but not sure if it’ll cause problem in the future. What could be causing the log sequence not match while running xtrabackup?
Thanks!