0

I'm using CentOS 8 and I have a MariaDB 10.5.4 Galera set up with three nodes. Now, I want it to create a backup to my central server from time to time. I'm thinking of mysqldump but restoration would take a lot of time and mariabackup does not support remote backups (I think). So I'm thinking of creating a Master-Slave to from my galera cluster setup to a stand-alone setup on my central server then I run mariabackup from there like this:

enter image description here

For now my current set up is that I had my third node act as a backup for HAProxy and it is where mariabackup is currently running (see image and remove central server). But my boss wanted me to store backup on central and let central do the backup instead of the database server.

Are there any simple alternative? I'm thinking of following this guide, but it's a bit outdated and I'm not sure if it would work. Thanks

1 Answer 1

1

Central backups occurring on a replica is a decent strategy.

The guide on quick glance looks ok. Ensure that your server-id is unique. Per mariadb galera guidance galera cluster members shoudl have the same server-id in most scenarios.. Its unclear why binlog-format=mixed when galera requires row so I'd just keep row.

'log-slave-updates' is the critical thing of the master node but for consistency its easy enough to have this on all galera nodes in case you need to change master at some point.

Like all backups consider the process that a restoration would take and business requirements on MTTR (mean time to recover). And test the restoration process when you've got backup to see it works and how long it takes.

6
  • So the galera nodes can have the same server_id of 01? I'll give this a try, thanks!
    – Gwynn
    Jul 22, 2020 at 0:22
  • server id is a numeric so leading 0 has no effect. Recommend reading galera server id official docs like I should of before writing this answer.
    – danblack
    Jul 22, 2020 at 3:53
  • Hello, kinda came up with this problem just now, is it possible to set up multiple master to a single slave, like one master contains the dev database and the other contains production database then they all send data to my central server, since I cant have 2 instances on of mariadb on my server. And another server would be costly.
    – Gwynn
    Jul 22, 2020 at 16:36
  • new problems are for new questions, however look at Multi-Source Replication and create new question if you have troubles/need further clarification. Mark this answer as correct if you are happy with it.
    – danblack
    Jul 22, 2020 at 23:57
  • Well, I'm just thinking far ahead of my current tasks, anyway what does this mean gitd_domain_id should be set to a different value on all nodes ? does this mean that one of my nodes should be 1, the other is 2, then the other is 3?
    – Gwynn
    Jul 23, 2020 at 0:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.