Awesome article, So I think its a nice trick if you don’t use xtrabackup or meb(mysql enterprise backup), because It would be more efficient using one of these tools for your backups strategies. Thanks for sharing this one with us.

Take care.

That is what I explain in the second paragraph. I will quote here for clearness:

> You need to make sure to run a single mysqlbinlog command with all related binlogs, and pipe them to mysql at once.

Thanks for stopping by.

Thanks for pointing it out. Similar approach and can be done with a single instance.

Cheers.

Thanks for your comment. Yes, if the file becomes big and fail for some reason, it becomes a problem.

shell> mysqlbinlog binlog.000001 | mysql -u root -p # Creates tmp table X
shell> mysqlbinlog binlog.000002 | mysql -u root -p # Uses tmp table X

but

shell> mysqlbinlog binlog.000001 binlog.000002 | mysql -u root -p

instead.

See the docs: https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery.html

There is even a better approach then playing with a second instance of MySQL, check this post: http://lefred.be/content/howto-make-mysql-point-in-time-recovery-faster/

Cheers 😉

and then
mysql < binlog.txt

Although if there are too many files to execute then this single file might become large.