Setting Up Replication - Source

Revision: 131807
Utilizador: Ulisses Coelho
Date: 2023-11-01 13:45

<<include slug="replica_slave">>
<<toc>>
Getting [[replication]] working involves steps on both the master server/s and steps on the slave server/s.

<<style class="bluebox">>
MariaDB 10.0 introduced replication with [[global-transaction-id|global transaction IDs]]. These have a number of benefits, and it is generally recommended to use this feature from MariaDB 10.0.
<</style>>

== Setting up a Replication Slave with Mariabackup

If you would like to use [[mariabackup|Mariabackup]] to set up a replication slave, then you might find the information at [[setting-up-a-replication-slave-with-mariabackup|Setting up a Replication Slave with Mariabackup]] helpful.

== Versions
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  [[#replicating-from-mysql-master-to-mariadb-slave|Replicating from MySQL Master to MariaDB Slave]].

== Configuring the Master
*Enable binary logging if it's not already enabled. See [[activating-the-binary-log|Activating the Binary Log]] and [[binary-log-formats|Binary log formats]] for details.
*Give the master a unique [[replication-and-binary-log-system-variables/#server_id|server_id]]. All slaves must also be given a server_id. This can be a number from 1 to 2^^32^^-1, and must be unique for each server in the replicating group.
* Specify a unique name for your replication logs with [[mysqld-options-full-list#-log-basename|--log-basename]]. If this is not specified your host name will be used and there will be problems if the hostname ever changes.
*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 [[configuring-mariadb-with-mycnf|my.cnf]] file and restart the database.
<<code>>
[mariadb]
log-bin
server_id=1
log-basename=master1
binlog-format=mixed
<</code>>

The server id is a unique number for each MariaDB/MySQL server in your network.
[[binary-log-formats|binlog-format]] specifies how your statements are logged. This mainly affects the size of the [[binary-log|binary log]] that is sent between the Master and the Slaves.

Then execute the following SQL with the [[mysql-command-line-client|{{{mysql}}}]] command line client:
<<sql>>
CREATE USER 'replication_user'@'%' IDENTIFIED BY 'bigs3cret';
GRANT REPLICATION SLAVE ON *.* TO 'replication_user'@'%';
<</sql>>

===Example Enabling Replication for MySQL

If you want to enable replication from MySQL 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##.

<<code>>
[mysqld]
log-bin
server_id=1
<</code>>

== Settings to Check
There are a number of options that may impact or break replication. Check the following settings to avoid problems.
* [[server-system-variables#skip_networking|skip-networking]]. If ##skip-networking=1##, the server will limit connections to localhost only, and prevent all remote slaves from connecting.
* [[server-system-variables/#bind_address|bind-address]]. Similarly, if the address the server listens for TCP/IP connections is 127.0.0.1 (localhost), remote slaves connections will fail.

== Configuring the Slave
*Give the slave a unique [[replication-and-binary-log-server-system-variables#server_id|server_id]]. All servers, whether masters or slaves, are given a server_id. This can be a number from 1 to 2^^32^^-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.

== Getting the Master's Binary Log Co-ordinates
Now you need prevent any changes to the data while you view the binary log position. You'll use this to tell the slave at exactly which point it should start replicating from.
* On the master, flush and lock all tables by running <<code inline='true'>>FLUSH TABLES WITH READ LOCK<</code>>. Keep this session running - exiting it will release the lock.
* Get the current position in the binary log by running ##[[show-master-status|SHOW MASTER STATUS]]##:
<<code>>
SHOW MASTER STATUS;
+--------------------+----------+--------------+------------------+
| File               | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--------------------+----------+--------------+------------------+
| master1-bin.000096 |      568 |              |                  |
+--------------------+----------+--------------+------------------+
<</code>>
*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 slave. See [[backup-restore-and-import|Backup, Restore and Import]] 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 slave has imported the data.
*Once the data has been copied, you can release the lock on the master by running [[transactions-lock|UNLOCK TABLES]].
<<code>>
UNLOCK TABLES;
<</code>>

== Start the Slave
*Once the data has been imported, you are ready to start replicating. Begin by running a [[change-master-to|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. For example:
<<sql>>
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;
<</sql>>

If you are starting a slave 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)
<<product mariadb from=10.0>>
MariaDB 10.0 introduced global transaction IDs (GTIDs) for replication. It is generally recommended to use (GTIDs) from MariaDB 10.0, as this has a number of benefits. All that is needed is to add the ##MASTER_USE_GTID## option to the ##CHANGE MASTER## statement, for example:
<<sql>>
CHANGE MASTER TO MASTER_USE_GTID = slave_pos
<</sql>>
See [[global-transaction-id|Global Transaction ID]] for a full description.
<</product>>

*Now start the slave with the [[start-slave|{{{START SLAVE}}}]] command:
<<sql>>
START SLAVE;
<</sql>>

*Check that the replication is working by executing the [[show-slave-status|{{{SHOW SLAVE STATUS}}}]] command:
<<sql>>
SHOW SLAVE STATUS \G
<</sql>>

*If replication is working correctly, both the values of {{{Slave_IO_Running}}} and {{{Slave_SQL_Running}}} should be {{{Yes}}}: 
<<code>>
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
<</code>>

== Replicating from MySQL Master to MariaDB Slave

* Replicating from MySQL 5.5 to MariaDB 5.5+ should just work. When using a MariaDB 10.2+ as a slave, it may be necessary to set [[replication-and-binary-log-server-system-variables/#binlog_checksum|binlog_checksum]] 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 starting from MariaDB 10.0.22 and MariaDB 10.1.8. In this case MariaDB will remove the MySQL GTIDs and other unneeded events and instead adds its own GTIDs.

== See Also
* [[binary-log-formats|Differences between Statement-based, mixed and row logging]]
* [[replication-and-foreign-keys|Replication and Foreign Keys]]
* [[replication-as-a-backup-solution|Replication as a Backup Solution]]
* [[multi-source-replication|Multi-source Replication]]
* [[global-transaction-id|Global Transaction ID]]
* [[parallel-replication|Parallel Replication]]
* [[replication-and-binary-log-server-system-variables|Replication and Binary Log System Variables]]
* [[replication-and-binary-log-status-variables|Replication and Binary Log Status Variables]]
* [[semisynchronous-replication|Semisynchronous Replication]]
* [[delayed-replication|Delayed Replication]]
* [[mariadb-vs-mysql-compatibility/#replication-compatibility|Replication Compatibility]]

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.

Setting Up Replication - Source

Products

Solutions

Resources

Company

Pricing

Download MariaDB