Not the answer you need?
Register and ask your own question!

how to get consistent binlog position LOCK TABLES FOR BACKUP + LOCK BINLOG FOR BACKUP

zergrushablezergrushable EntrantInactive User Role Beginner
as per this article this is the xtrabackup workflow:

LOCK TABLES FOR BACKUP ... copy .frm, MyISAM, CSV, etc. ... LOCK BINLOG FOR BACKUP UNLOCK TABLES ... get binlog coordinates ... ... wait for redo log copying to finish ... UNLOCK BINLOG
I don't have enough knowledge on how "FOR BACKUP" is working under the hood and i'm a bit confused in "get binlog coordinates" step. If LOCK BINLOG FOR BACKUP is after LOCK TABLES FOR BACKUP there is not a risk of getting a position newer then mysql data?
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.