Follow this step-by-step guide to configure standard replication. Learn how to prepare the primary, configure the replica, and establish a connection for data synchronization.
Getting replication working involves steps on both the master server/s and steps on the replica server/s.
If you want to use to set up a replication replica, review the information under .
Setting up replication the "traditional" way is covered below.
In general, when replicating across different versions of MariaDB, it is best that the master is an older version than the slave. MariaDB versions are usually backward compatible, while of course older versions cannot always be forward compatible. See also .
Follow these steps to set up MariaDB replication:
Configure the Master
Enable binary logging if it's not already enabled. See and for details.
Give the master a unique . All slaves must also be given a server_id. This can be a number from 1 to 232-1, and must be unique for each server in the replicating group.
This page is licensed: CC BY-SA / Gnu FDL
Slaves will need permission to connect and start replicating from a server. Usually this is done by creating a dedicated slave user, and granting that user permission only to replicate (REPLICATION SLAVE permission).
Example Enabling Replication for MariaDB
Add the following into your my.cnf file and restart the database.
The server id is a unique number for each MariaDB/MySQL server in your network.binlog-format specifies how your statements are logged. This mainly affects the size of the binary log that is sent between the Master and the Replicas.
Then execute the following SQL with the mysql command line client:
Example Enabling Replication for MySQL
If you want to enable replication from MySQL 5.7 or earlier to MariaDB, you can do it in almost the same way as between MariaDB servers. The main difference is that MySQL doesn't support log-basename.
Replication from MySQL 8.0 to MariaDB .
Check Settings
There are a number of options that may impact or break replication. Check the following settings to avoid problems.
skip-networking. If skip-networking=1, the server will limit connections to localhost only, and prevent all remote replicas from connecting.
bind-address. Similarly, if the address the server listens for TCP/IP connections is 127.0.0.1 (localhost), remote replica connections will fail.
Configure the Replica
Give the replica a unique server_id. All servers, whether masters or replicas, are given a server_id. This can be a number from 1 to 232-1, and must be unique for each server in the replicating group. The server will need to be restarted in order for a change in this option to take effect.
Get the Master's Binary Log Coordinates
Now you need prevent any changes to the data while you view the binary log position. You'll use this to tell the replica at exactly which point it should start replicating from.
On the master, flush and lock all tables by running FLUSH TABLES WITH READ LOCK. Keep this session running - exiting it will release the lock.
Get the current position in the binary log by running SHOW MASTER STATUS:
Record the File and Position details. If binary logging has just been enabled, these will be blank.
Now, with the lock still in place, copy the data from the master to the replica. See for details on how to do this.
Note for live databases: You just need to make a local copy of the data, you don't need to keep the master locked until the replica has imported the data.
Once the data has been copied, you can release the lock on the master by running .
Start the Replica
Once the data has been imported, you are ready to start replicating. Begin by running a CHANGE MASTER TO, making sure that MASTER_LOG_FILE matches the file and MASTER_LOG_POS the position returned by the earlier SHOW MASTER STATUS:
If you are starting a replica against a fresh master that was configured for replication from the start, then you don't have to specify MASTER_LOG_FILE and MASTER_LOG_POS.
Use Global Transaction ID (GTID)
It is generally recommended to use (GTIDs), as it has a number of benefits. All that is needed is to add the MASTER_USE_GTID option to the CHANGE MASTER statement:
See for a full description.
Now start the replica with the statement:
Check that the replication is working by executing the command:
If replication is working correctly, both the values of Slave_IO_Running and Slave_SQL_Running should be Yes:
Replicating from MySQL Master to MariaDB Replica
Replicating from MySQL 5.5 to MariaDB should just work. When using a MariaDB as a replica, it may be necessary to set to NONE.
Replicating from MySQL 5.6 without GTID to MariaDB 10+ should work.
Replication from MySQL 5.6 with GTID, binlog_rows_query_log_events and ignorable events works. In this case MariaDB will remove the MySQL GTIDs and other unneeded events and instead adds its own GTIDs.
requires or newer.
SHOW MASTER STATUS;
+--------------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--------------------+----------+--------------+------------------+
| master1-bin.000096 | 568 | | |
+--------------------+----------+--------------+------------------+CHANGE MASTER TO
MASTER_HOST='master.domain.com',
MASTER_USER='replication_user',
MASTER_PASSWORD='bigs3cret',
MASTER_PORT=3306,
MASTER_LOG_FILE='master1-bin.000096',
MASTER_LOG_POS=568,
MASTER_CONNECT_RETRY=10;[mariadb]
log-bin
server_id=1
log-basename=master1
binlog-format=mixedCREATE USER 'replication_user'@'%' IDENTIFIED BY 'bigs3cret';
GRANT REPLICATION SLAVE ON *.* TO 'replication_user'@'%';[mysqld]
log-bin
server_id=1UNLOCK TABLES;CHANGE MASTER TO MASTER_USE_GTID = slave_posSTART REPLICA;SHOW REPLICA STATUS \GSlave_IO_Running: Yes
Slave_SQL_Running: Yes