If the mysql-replication is broken, there are two ways to fix the problem: skip the error rebuild the replication In some cases you could easily skip error. If you for example execute the same INSERT on both server. Skip the error Login into mysql as root: STOP SLAVE; SET GLOBAL […]
In contrast to a master-slave replication in a master-master replication changes made on one server are immediately available on both. The setup of a master-master-replication is similar to a master-slave-replication. I show here only the differences (for the basics see mysql master-slave-replication). In the following to old master remains as […]
In a master-slave replication on the slave are the databases of the master 1:1 available. Changes performerd on the master are immediately available on the slave (as long as you don´t user master_delay). Thus, it is not a true backup solution. Master setup: Change the section [mysqld] in /etc/my.cnf. Make […]
Here is the addition to fail2ban mit xt_recent. Fail2ban can ban ip only until the server restarts. I therefore add the bans not only in the firewall, but store them also into a mysql database. Basics I´ve created the database systemlog which containing two tables – one for the configs […]