an "rsync" with the right options from the unaffected slave to the corrupt one might prove to be an elegant technique
Kishore Jalleda On 3/7/06, Michael Jeung <[EMAIL PROTECTED]> wrote: > > Hi Folks, > > We've got a Single Master/Multiple Slave environment. > Recently, we had some corruption on one of the slaves and I had to > repair the affected tables. > > After the repair completed, some of the rows on the slave had been > deleted - so the Master and the Slave weren't exactly in synch. The > slave was missing some records. I verified this myself with a > select count(*) on the table. > > Now, I know this is the normal way for MySQL to repair it's database. > > However, what I'd like to do is restore these missing rows to the > Slave without doing a dump and reload from my backups. Is this > possible? > > The way that we normally approach this problem is to take an > unaffected slave and copy the mysql directory from an unaffected > slave over to the corrupt slave. Then we restart MySQL on the > corrupt slave and things work out without too much difficulty. > However, this has always seemed like a terrible way to restore a > corrupt slave to me. Is there a more elegant way to do it? > > Regards, > Michael Jeung > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > >
