The easiest and most straightforward method for setting up replication is to use new master and slave servers.
You can also use this method if you are setting up new servers but have an existing dump of the databases from a different server that you want to load into your replication configuration. By loading the data into a new master, the data will be automatically replicated to the slaves.
To set up replication between a new master and slave:
Configure the MySQL master with the necessary configuration properties. See Section 220.127.116.11, “Setting the Replication Master Configuration”.
Start up the MySQL master.
Set up a user. See Section 18.104.22.168, “Creating a User for Replication”.
Obtain the master status information, or a copy of the master's binary log index file made during a shutdown for the data snapshot. See Section 22.214.171.124, “Obtaining the Replication Master Binary Log Coordinates”.
On the master, release the read lock:
mysql> UNLOCK TABLES;
On the slave, edit the MySQL configuration. See Section 126.96.36.199, “Setting the Replication Slave Configuration”.
Start up the MySQL slave.
CHANGE MASTER TOstatement to set the master replication server configuration. See Section 188.8.131.52, “Setting the Master Configuration on the Slave”.
Perform the slave setup steps on each slave.
Because there is no data to load or exchange on a new server configuration you do not need to copy or import any information.
If you are setting up a new replication environment using the data from a different existing database server, you will now need to run the dump file generated from that server on the new master. The database updates will automatically be propagated to the slaves:
shell> mysql -h master < fulldb.dump