Hello, Our strategy for all our vms, including mariadb, is entire vm level snapshot using Veeam. Every 3 hours, with offsite copies to another datacentre each 24h and a second offsite copy on tapes.
We’ve tested this many times and it’s quite reliable. Usually when a user has deleted data from something in error and wants it back. In which case we restore the vm to a different IP and they can connect and recover what data they want and re-add it it to the live server. One case requires some special handling, which is a replicated copy (using the traditional replica model), where we have to ensure the secondary vm is not restored ahead of the primary. Otherwise recovery “just works”. And of course, we get the usual vm benefits of being able to snapshot ahead of updates and so on. S From: Zoe Kron via discuss <[email protected]> Sent: 02 February 2026 12:06 To: [email protected] Subject: [MariaDB discuss] Backup Strategy Hello List, I am trying to draw a concept of a MariaDB Backup Strategy. I am aware of full Backups (via Restic as outlined here: https://archive.fosdem.org/2022/schedule/event/mariadb_backup_restic/attachments/slides/5135/export/events/attachments/mariadb_backup_restic/slides/5135/mariabackup_restic.pdf) I am searching through the net and could not find a good solution for Binlogs. Postgres f.e. has WAL Archiving to a remote Storage or onto a Master. How can I do something like this with MariaDB (without MaxScale Binlog Router). Can in a Master-Slave Replica the Binlogs be synced or are they only synced and deleted after replication? Is there a remote solution (S3?) I suspect there has to be some solutions deployed in companies, universities ...). The max. loss is usually Last commit (Full backup + Binlog). Would be glad for any help as I am at the end of my knowledge and the net does not seem to know a lot about this :D Kindly Zoë
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
