To fix a corruption problem in a replication master database, you can restore the backup, taking care not to propagate unnecessary SQL operations to the slave servers:
Using the backup of the master database, do the
apply-log operation, shut down the database,
and do the
Edit the master
my.cnf file and comment
log-bin, so that the slaves do not
receive twice the binlog needed to recover the master.
Replication in the slaves must be stopped temporarily while you pipe the binlog to the master. In the slaves, do:
mysql> STOP SLAVE;
Start the master mysqld on the restored backup:
$ mysqld … InnoDB: Doing recovery: scanned up to log sequence number 0 64300044 InnoDB: Last MySQL binlog file position 0
5585832, file name ./
InnoDB prints the binlog file and the position it was able to recover to.
Pipe the remaining binlog files to the restored backup. For
example, if there are two more binlog files,
$ mysqlbinlog --start-position=5585832 mysqldatadir/omnibook-bin.002 | mysql $ mysqlbinlog /mysqldatadir/omnibook-bin.003 | mysql $ mysqlbinlog /mysqldatadir/omnibook-bin.004 | mysql
The number of remaining binlog files varies depending on when the last backup was taken: the older the backup, the more remaining binlog files there may be.
The master database is now recovered. Shut down the master and
my.cnf to uncomment
Start the master again.
Start replication in the slaves again:
mysql> START SLAVE;
Copyright © 2003, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices