


The servers used in this example have the following IP addresses:īind-address = 10.10.8.164 server-id = 2 log_bin = /var/log/mysql/mysql-bin.log If your hosting provider doesn’t support private IP addresses, you can use the public IP addresses and configure your firewall to allow traffic on port 3306 only from trusted sources. We’re assuming that you have two servers running Debian 10, communicating with each other over a private network. This type of replication topology is best suited for deploying of read replicas for read scaling, live databases backup for disaster recovery, and for analytics jobs. MariaDB is the default implementation of MySQL in Debian. In this guide, we will show you how to set up MariaDB Master/Slave replication with one master and one slave server on Debian 10. By default, the replication is asynchronous where the master sends events that describe database modifications to its binary log and slaves request the events when they are ready. MySQL supports several replication topologies with Master/Slave topology being one of the most well-known topologies in which one database server acts as the master, while one or more servers act as slaves.
