MySQL Forums
Forum List  »  Replication

Re: Replace replication slave after long downtime
Posted by: Rick James
Date: March 11, 2014 05:56PM

If you have another slave that is up-to-date, I would do the following:

* Stop mysqld on the good slave
* Copy the mysql tree to the dead slave
* Restart mysqld on on good slave (put it back online)
* verify that server_id is different on dead slave
* Start everything on dead slave -- it will pick up on replication where the good slave left off. It should be caught up very fast.

If the above works, then the binlogs are not of any use.

If you don't have a 'good slave', then some other procedure is needed. Do you have _all_ the binlogs since creation?

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Replace replication slave after long downtime
1005
March 11, 2014 05:56PM


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.