Zoe Kron via discuss <[email protected]> writes: > I am trying to draw a concept of a MariaDB Backup Strategy.
> 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. Indeed, backup of binlogs has currently somewhat limited options. One way that should work is O/S-level filesystem (eg. Btrfs) or disk (eg. LVM) snapshots, which requires that the binlogs are on the same filesystem as the other data to be backed up. This requires that innodb_log_at_trx_commit=1|2, and does not work for non-transactional table updates (eg. MyISAM). But mysqldump or mariabackup currently does not allow to backup the binlogs, unfortunately. In the upcoming MariaDB 12.3 release, there is an improved binlog format enabled with --binlog-storage-engine=innodb. With this format, binlogs are included in the backup taken with mariabackup, so that is one additional option going forward. > 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?) When the slave is run with --log-slave-updates, the slave keeps a copy of the binlog that is equivalent to the one on the master, and that copy is updated with every commit of the slave. This means that at the loss of the master, the slave has a copy of the binlogs as well as a copy of the data (for any data that was replicated before the loss of the master). So replication is a usual way to have copies/backup of the binlogs, yes. Hope this helps, - Kristian. _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
