Re: Replication newbie: 5.6

[Rick James]

First, let me understand what you have and what you want.

You have:
A -- production server
B, C -- no data on them
No replication set up now.

You want:
C -> B -- That is, C is Master, B is its only Slave
A will be retired.

* Are those (You have/want) correct?
* Are you using InnoDB? or MyISAM? (Downtime is greater for MyISAM.)
* How much data is there and how much downtime can you afford?
With those answers, we can continue this thread.

Also look at XtraDbBackup (from Percona); they have good magic, too.
(I am not familiar with mysqlreplicate.)

The _first_ Slave you build requires dumping all the data from the Master. This impacts the Master.
Subsequent Slaves (hanging off the same Master) can impact just the Slave -- by cloning that Slave. (Perhaps this is not relevant for your situation.)
Once the topology is established and there is data everywhere, replication is continual and 'magic'. (OK, there can be glitches.)