I have a 3 node Galera cluster with keepalived and HAproxy. There is a virtual IP that primarily stays on one node, but will float to one of the other nodes should the primary become unavailable. I have noticed that when Veeam performs a backup of the virtual machines hosting the cluster, I lose database connectivity from my client applications (Zabbix and FreeRADIUS).
I've tried to correct this problem by having Veeam perform backup on the primary node 30 minutes after it has completed the other 2, with the thought that the IP would move to another machine when the primary becomes unavailable during the snapshot period. This, however, does not work, as I am seeing my log files at the time of backup filling with things like this from the Zabbix server:
13073:20181126:033533.943 [Z3005] query failed:  Lost connection to MySQL server during query...
Looking through the logs from the primary node, I believe that since the VM is in a frozen state, it cannot tell one of the other nodes to pick up the IP address, leading to the dB connection failure.
Is there a way to run a pre-freeze (and post-thaw) script to manually move the IP to a different node and have it be cluster aware? I've tried taking down keepalived, but cluster control automatically restarts it and moves the IP back to the machine (as expected).
Please sign in to leave a comment.