MySQL master to master replication database servers

Reviews, software, hardware and electronics.

Moderator: embleton

Post Reply
User avatar
Site Admin
Posts: 476
Joined: Sat Aug 02, 2014 1:40 pm
Location: Plymouth

MySQL master to master replication database servers

Post by embleton » Tue Jul 10, 2018 10:18 pm

We assume that the mysql package has been set up on the primary master and secondary master server. The configuration file we deal with first is located at /etc/mysql with its name being mysql.cnf and this needs to be modified first after exporting the database with phpMyAdmin package. Information on the package is at but it is an easy package to install on ubuntu.

Server A: = Server B: # master to master MySQL replication servers. Ubuntu 17.x.x and 18.x.x

Export the data from the current system or the primary server with the phpMyAdmin package. Ensure that none of the databases is read by any package or internet access for that'll destroy the pointers into the database. The MySQL database will be offline until the secondary is in operation.

Modify the mysql.cnf file as follows the primary master server A.

# start of the configuration file.
server-id = 67345215 # this number needs to be unique across the primary and secondary masters.
sync_binlog=1 # even though this causes greater disk I/O for it flushes the data immediately to disk.
binlog_do_db=database # This should be the same name as the database in the schemas.
# end of the configuration file but all statements in the standard file
# should remain after this statements that have been added.
The above statements are the only ones necessary and there should be no binding addresses with bind-address= in the configuration which many specify in their method of setting up the master to master replication.

Modify the mysql.cnf file as follows on the secondary master server B.

server_id = 1231654587
# bind-address =

Now we should create users for the replication process with and at the command terminal on the primary and secondary masters (and slaves).

mysql -u root -p

create user 'replicator'@'%' identified by 'password';

grant replication slave on *.* to 'replicator'@'%';

flush privileges;

The rest of the process can be done in the phpMyAdmin package on the access to that package on the primary and secondary master websites. By entering the primary master the replication page is executed once one has logged on to the primary MySQL database with its root and password for the root on the website for primary and secondary masters. The route for creating the primary master on each server can be run once the MySQL server is restarted on the primary and secondary master with.

sudo service mysql restart

The scary bit is if the database belongs on the secondary master then the database must be dropped. This can be done in the phpMyAdmin website on the secondary master. The export of the database should now be imported into the secondary primary master replicator. Select the option 'change or reconfigure master'. The replicator username can be used at this stage with the IP address of the secondary master replication. Move to the secondary and follow the same process of not forgetting the IP address is that of the primary master replication server. The slave can now be started on each primary master servers by selecting the option 'Control slave' and then perform a full start on each server.

And that is it both servers should be up and running and one has a master to master replication MySQL databases. This is known to work for this IPv4 & IPv6 site and IPv6 only are in a live master to master replication MySQL database for the written content.

Post Reply