Jure Pečar wrote: > On Tue, 23 May 2006 15:32:31 -0700 > Mace Eliason <meliason at shaw.ca> wrote: > > > >>My only question is I have found in the system that I setup with >>mysql replication it worked great but if you remove one of the >>servers and put it back in you have to stop mysql and copy over the >>newer database and then restart both to get it to replicate >>correctly. >> >>Is there a way to get replication to work so it will automatically >>sync the master and slave without having to stop and copy and restart? > > > This is only neccessary if somethign ugly happens to your binary logs so the syncing thread of mysql has nowhere to get the good data from. Usually this should not happen. I only had it hapen when I run out of disk space. > I suggest you check your setup and mysql replication docs again. > Hi - I, too, suggest this. I have a setup which is similar to what you're going for, I think. The MySQL part utilizes master-master replication, or multi-master replication, which gives me a hot spare just in case. In the event that one of these machines fail, it is updated automagically when it comes back online, by it's "master". MySQL has detailed this procedure pretty well. Take a look at it and see what you can find. Thanks -dant