Comments on: MySQL Replication: Redundancy http://rackerhacker.com/2008/01/03/mysql-replication-redundancy/ Words of wisdom from a server administrator Fri, 10 Feb 2012 00:55:08 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Patrick http://rackerhacker.com/2008/01/03/mysql-replication-redundancy/#comment-15560 Patrick Mon, 26 Oct 2009 21:56:58 +0000 http://rackerhacker.com/2008/01/03/mysql-replication-redundancy/#comment-15560 Hi, exactly the information Iwas looking for. i'm wondering if I dont want to setup the original master(lets call A) as a slave, what would be the procedure to change the new master back to the slave(lets call B) once the original master can be recovered. I guess we are assuming the new master has been in use for a few days and has new data, and either the original master has no data or data in state from few days ago. Does the following sound correct? 1) do a flush table with read lock on B 2) do a mysqldump on B and load into A. Now data should be same on A and B. 3) show master status on A to record binlog file and position 4) use CHANGE MASTER to on B to update new position and binlog. 5) START SLAVE on B. Hi,
exactly the information Iwas looking for.

i'm wondering if I dont want to setup the original master(lets call A) as a slave, what would be the procedure to change the new master back to the slave(lets call B) once the original master can be recovered. I guess we are assuming the new master has been in use for a few days and has new data, and either the original master has no data or data in state from few days ago.
Does the following sound correct?

1) do a flush table with read lock on B
2) do a mysqldump on B and load into A. Now data should be same on A and B.
3) show master status on A to record binlog file and position
4) use CHANGE MASTER to on B to update new position and binlog.
5) START SLAVE on B.

]]>