The simplest method may be to set them up in a multi-master configuration, similar to what's documented here: http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html
This way you won't have to worry about switching between two masters in a failover scenario since they're both writable. -Aaron On Wed, Jul 8, 2009 at 1:38 PM, Cantwell, Bryan <bcantw...@firescope.com>wrote: > I have successfully set up a replication master/slave scenario with my > MySQL 5.0.51a > Now in the event of a fail over to the slave (an identical appliance), I > want the old master to become the slave for an eventual switch back the > other way. > Would it really take the same process to keep the old master up to date > with the new one? Or is there a way to bring it up to date with the new > machine without a mysqldump or copying data files? > > I have binary logging running on both machines in hopes that I could just > tell the new slave how to catch up with the new master... > Any assistance here? > > thanks > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=aaronb...@gmail.com > >
