For many years, MySQL replication used to be based on binary log events. It was considered that all a slave knew was the exact event and the exact position it just read from the master. Any single transaction from a master could have ended in different binary logs, and also, in different positions in these logs. GTID was introduced along with MySQL 5.6. It has brought, along, some major changes in the way MySQL operates. Every transaction has a unique identifier which identifies it in a same way on every server. It’s not important, anymore, in which binary log position a transaction was recorded, all you need to know is the GTID. Database replication is used to handle multiple copies of data, automatically, from the master database server to slave database servers. If we have changed data or schema in the master database, it will, automatically, update the slave database. The main advantage of replication is that it prevents the data loss. If the master database server is crashed, the exact copy of data will be there in the slave server. In MySQL, you can use MySQL Utility for implementing database replication between master and slave. MySQL Utility is a package that is used for maintenance and administration of MySQL servers. You can install MySQL utility, along with MySQL Workbench, or install it as a stand-alone package. MySQL Replication. This article explains how it is implemented, with an example. In this example, two servers have been used – one master and one slave. Both servers are configured in the same manner with MySQL server and MySQL Utility.

1. MySQL Database Replication using GTID
By Aneesha K.A,
.Net Developer, RapidValue

2. MySQL Replication
© RapidValue Solutions l 2
Introduction
Database replication is used to handle multiple copies of data, automatically, from the
master database server to slave database servers. If we have changed data or schema
in the master database, it will, automatically, update the slave database.
The main advantage of replication is that it prevents the data loss. If the master
database server is crashed, the exact copy of data will be there in the slave server.
In MySQL, you can use MySQL Utility for implementing database replication between
master and slave. MySQL Utility is a package that is used for maintenance and
administration of MySQL servers. You can install MySQL utility, along with MySQL
Workbench, or install it as a stand-alone package.
MySQL Replication
This article explains how it is implemented, with an example. In this example, two
servers have been used – one master and one slave. Both servers are configured in the
same manner with MySQL server and MySQL Utility.
Following are the steps used to implement replication:
1. Enable GTID mode on both servers.
o GTID is global transaction identifier that is associated with each transaction
committed on the master database. GTID is the combination of 128 bit Server
UUID and one transaction Identifier number like this 8fe8b710-cd34-11e4-824d-
fa163e52e544:100
o You need to enable the following in the My.ini configuration file of MySQL
servers.
gtid-mode=on
enforce-gtid-consistency=true
Master Database Server – My.ini

3. MySQL Replication
© RapidValue Solutions l 3
Slave Database Server –My.ini
2. Grant remote access to both servers by executing following commands.
grant all on *.* to root@'%' with grant option;
3. Establish Replication between master and slave using mysqlreplicate
command.
mysqlreplicate –master=root:pwd@10.24.xx.xx:3306 –
slave=root:pwd@10.24.xx.xx:3306 –rpl-user=root:pwd
Output

4. MySQL Replication
© RapidValue Solutions l 4
4. Verify the Replication Status.
You need to establish replication between master and slave database server. You
can verify the replication by using following commands.
a. show master statusG
Output
b. show slave statusG

5. MySQL Replication
© RapidValue Solutions l 5
c. mysqlrplcheck –master=root:pwd@10.24.xx.xx:3306 –
slave=root:pwd@10.24.xx.xx:3306
Output
d. mysqlrplshow –master=root:pwd@10.24.xx.xx:3306 –discover-slaves-
login=root:pwd

6. MySQL Replication
© RapidValue Solutions l 6
Output
Health Monitoring and Failover
You can monitor the health status of master and slave by using mysqlrpladmin and
mysqlfailover command.
a. mysqlrpladmin
mysqlrpladmin –master=root:pwd@10.24.xx.xx:3306 --
slaves=root:pwd@10.24.xx.xx:3306 health
Output
b. mysqlfailover
mysqlfailover --master=root:pwd@10.24.xx.xx:3306 –discover-slaves-login=root:pwd
Output

7. MySQL Replication
© RapidValue Solutions l 7
mysqlfailover command monitors the health of slave and master server and if master
has failed, it will automatically promote one of the slave as master.
Conclusion
For many years, MySQL replication used to be based on binary log events. It was
considered that all a slave knew was the exact event and the exact position it just read
from the master. Any single transaction from a master could have ended in different
binary logs, and also, in different positions in these logs.
GTID was introduced along with MySQL 5.6. It has brought, along, some major changes
in the way MySQL operates. Every transaction has a unique identifier which identifies it
in a same way on every server. It’s not important, anymore, in which binary log position
a transaction was recorded, all you need to know is the GTID.

8. MySQL Replication
© RapidValue Solutions l 8
About RapidValue
RapidValue is a leading provider of end-to-end mobility, omnichannel and cloud solutions to enterprises
worldwide. Armed with a large team of experts in consulting, UX design and application engineering,
along with experience delivering global projects, we offer a range of services across various industry
verticals. RapidValue delivers its services to the world’s top brands and Fortune 1000 companies, and
has offices in the United States and India.
Disclaimer
This document contains information that is confidential and proprietary to RapidValue Solutions Inc. No
part of it may be used, circulated, quoted, or reproduced for distribution outside RapidValue. If you are
not the intended recipient of this report, you are hereby notified that the use, circulation, quoting, or
reproducing of this report is strictly prohibited and may be unlawful.
www.rapidvaluesolutions.com/blogwww.rapidvaluesolutions.com
+1 877.643.1850 contactus@rapidvaluesolutions.com