MySQL Forums
Forum List  »  Data Recovery

normal shutdown caused data loss
Posted by: lynda patterson
Date: May 15, 2009 03:38PM

I rebooted my server after some kernel updates this week, and when MySQL came back up the InnoDB tables were reverted back in time by 3 weeks!

I only have experience with backup and recovery on MyISAM tables (those were fine), so I have always just taken filesystem backups while the database was online. Unfortunately, in my tape backups the file mod time on the ibdata files and iblogfiles is that same 3-weeks-ago time (April 23).

I did not have the log-bin setting configured, so no binary logs (I just learned about these), and the parameter innodb_fast_shutdown=1. I wonder if either of these could have saved me?? Is there any way to recover the missing data, or did it get dumped when the server rebooted? Please help!

090513 14:01:10 [Note] /usr/libexec/mysqld: Normal shutdown

090513 14:01:10 InnoDB: Starting shutdown...
090513 14:01:14 InnoDB: Shutdown completed; log sequence number 0 145650203
090513 14:01:14 [Note] /usr/libexec/mysqld: Shutdown complete

090513 14:01:14 mysqld ended

090513 14:04:54 mysqld started
090513 14:04:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090513 14:04:54 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 143116820.
InnoDB: Doing recovery: scanned up to log sequence number 0 143116820
InnoDB: Last MySQL binlog file position 0 0, file name
090513 14:04:54 InnoDB: Started; log sequence number 0 143116820
090513 14:04:55 [Note] /usr/libexec/mysqld: ready for connections.

Edited 1 time(s). Last edit at 05/15/2009 03:40PM by lynda patterson.

Options: ReplyQuote

Written By
normal shutdown caused data loss
May 15, 2009 03:38PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.