[MDEV-5993] MySQL WL#4783 Extend mysqlbinlog to support remote backup of binary logs Created: 2014-04-01  Updated: 2016-03-10  Resolved: 2016-03-10

Status: Closed
Project: MariaDB Server
Component/s: Replication, Scripts & Clients
Fix Version/s: 10.2.0

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Alexey Botchkov
Resolution: Fixed Votes: 2
Labels: gsoc15, mysqlbinlog

Issue Links:
Duplicate
is duplicated by MDEV-8713 Add continuous binary log backup to m... Closed
PartOf
is part of MDEV-4784 merge test cases from 5.6 Stalled

 Description   

main.mysqlbinlog_raw_mode and main.mysqlbinlog_raw_mode_win covering this worklog: https://dev.mysql.com/worklog/task/?id=4783

MySQL needs a way of creating real-time backups.  The current method of doing
this is to create a slave with using the blackhole engine as can be seen at the
following URL:
http://dev.mysql.com/doc/refman/5.1/en/blackhole-storage-engine.html
 
This method works rather well but has the disadvantage of requiring a whole
MySQL instance to run to make the real-time backups, this can be a burden on
resources and difficult to setup if you are trying to backup many MySQL servers.
 
We already have mysqlbinlog to talk to remote MySQL servers to retrieve binlog
data and translate it into SQL statements so in theory it should be easy enough
to create a raw mode for the output.
 
Solution
mysqlbinlog has been modified to have several new parameters, key to this is the
new --raw flag which writes the data out in raw binlog format rather than
translating it.  The other parameter changes are designed to add more
functionality to the --raw flag so that it can easily be used in various backup
scenarios.



 Comments   
Comment by Colin Charles [ 2014-05-04 ]

This is now documented here:
http://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog-backup.html

This is in use by tools like MHA now as well: https://code.google.com/p/mysql-master-ha/wiki/Configuration#Binlog_server

Comment by Sergei Golubchik [ 2016-03-10 ]

Implemented as MDEV-8713

Generated at Thu Feb 08 07:08:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.