Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am in the process of migrating 2 DB servers (Master & Slave) to two new DB Servers (Master and Slave)

DB1 - Master (production)

DB2 - Slave (production)

DB3 - New Master

DB4 - New Slave

Currently I have the replication set up as:

DB1 -> DB2
DB3 -> DB4

To get the production data replicated to the new servers, I'd like to get it "daisy chained" so that it looks like this:

DB1 -> DB2 -> DB3 -> DB4

Is this possible? When I run show master status; on DB2 (the production slave) the binlog possition never seems to change:

| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
| mysql-bin.000020 |       98 |              |                  | 

I'm a bit confused as to why the binlog position is not changing on DB2, Ideally it will be the master to DB3.

share|improve this question
up vote 11 down vote accepted

The binlog on DB2 wasn't updating the slave updates. To daisy chain the replication, one must set log-slave-updates in my.conf.

share|improve this answer

Yes, it is possible :) This is called "Master with Relay Slave" replication and there a lot of documents about it on the net.

I'd recommend you to take a look at the official documentation here.

Btw, also take a look at these slides. They've some hints about replication topologies.

Hope this helps.

share|improve this answer

yes - you can daisy-chain mysql servers, you can even make a circular replication with two or more machines in it. just remember to enable binloging on slave that also acts as master.

share|improve this answer
Circular replication is incredibly fragile. It's ill-advised under most circumstances. – Warner May 25 '10 at 17:51
@Warner - this was just example of even more complicated replication setup. – pQd May 25 '10 at 19:03

Yes, it is possible. Realistically, you need a new snapshot of DB2 to build DB3. At that point, if you have a good position, you can either use than for DB4 or take another snapshot of DB3.

Don't forget to set unique server_id for each server.

High Performance MySQL is a great book for referencing more advanced MySQL administration.

share|improve this answer
DB2 is currently only a slave, but it's binlog position isn't changing... Do you know if that's normal? – mmattax May 25 '10 at 17:48
The slave (DB2) is up to date with the master, yet the binlog position isn't changing, what should I check? – mmattax May 25 '10 at 17:54
Yes, I've confirmed that I can change data on DB1 and it's replicated to DB2, yet DB2's binlog position is the same. – mmattax May 25 '10 at 17:57
I think DB@ isn't logging slave updates, hence why the position isn't changing:… – mmattax May 25 '10 at 18:06

Why not just add DB3 as a new slave, and then promote it to master when you're ready to make the switch? This would give you the temporary added benefit of having multiple slaves, and reduce or eliminate your downtime.

share|improve this answer
that's exactly what I am doing... – mmattax Jun 4 '10 at 17:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.