Announcement Module
No announcement yet.

How to skip - InnoDB Crash recovery

Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to skip - InnoDB Crash recovery

    We clone the data from a standby server(S1) in which data replicated from a active master(M) by doing stop slave in standby(S1) to create new standby server(S2) like M --> S1 ---> S2

    The data will be consistent in this approach but while starting the S2 it goes to INNODB crash recovery & takes long time to start.

    Data size will be approx 300 GB that spans across 150 database with approx 1.5 Million tables

    How to Overcome this ?

    We do the following steps.,

    Stop slave S1
    Flush logs S1
    Mark the positions (bin log file)
    Unzip mysql kit in s2
    rsync ibdata iblog* & data/* files to S2 from S1
    And start the server in S2


  • #2

    With this method as is is dangerous - you could be missing a lot of data still in memory this way which InnoDB will not pickup during recovery. I suggest taking the XtraBackup route instead _up_replication.html
    Our documentation has a lot of answers about common questions on Percona software, have you checked there before posting that question here?

    Join us at the annual Percona Live MySQL Users Conference -