When the Lockless binary log information
feature is available  on the server, Percona XtraBackup can trust
binary log information stored in the InnoDB system header and avoid executing
LOCK BINLOG FOR BACKUP (and thus, blocking commits for the duration of
REDO log copy) under a number of circumstances:
xtrabackup --slave-infooption is not specified)
If all of the above conditions hold, Percona XtraBackup does not execute the
SHOW MASTER STATUS as a part of the backup procedure, does not create the
xtrabackup_binlog_info file on backup. Instead, that information is
retrieved and the file is created after preparing the backup, along with
xtrabackup_binlog_pos_innodb, which in this case contains
exactly the same information as in
xtrabackup_binlog_info and is thus
To make this new functionality configurable, there is now a new Percona XtraBackup option,
xtrabackup --binlog-info, which can accept the
OFF- This means that Percona XtraBackup will not attempt to retrieve the binary log information at all, neither during the backup creation, nor after preparing it. This can help when a user just wants to copy data without any meta information like binary log or replication coordinates. In this case,
xtrabackup --binlog-info=OFFcan be passed to Percona XtraBackup and
LOCK BINLOG FOR BACKUPwill not be executed, even if the backup-safe binlog info feature is not provided by the server (but the backup locks feature is still a requirement).
ON- This matches the old behavior, i.e. the one before this Percona XtraBackup feature had been implemented. When specified, Percona XtraBackup retrieves the binary log information and uses
LOCK BINLOG FOR BACKUP(if available) to ensure its consistency.
LOCKLESS- This corresponds to the functionality explained above: Percona XtraBackup will not retrieve binary log information during the backup process, will not execute
LOCK BINLOG FOR BACKUP, and the
xtrabackup_binlog_infofile will not be created. The file will be created after preparing the backup using the information stored in the InnoDB system header. If the required server-side functionality is not provided by the server, specifying this
xtrabackup --binlog-infovalue will result in an error. If one of the above mentioned conditions does not hold,
LOCK BINLOG FOR BACKUPwill still be executed to ensure consistency of other meta data.
AUTO- This is the default value. When used, Percona XtraBackup will automatically switch to either
LOCKLESS, depending on the server-side feature availability, i.e., whether the
have_backup_safe_binlog_infoserver variable is available.
|||This feature is exclusive to Percona Server starting with version
5.6.26-74.0. It is also used in Percona XtraDB Cluster starting with
version 5.6.26-25.12 when the node is being backed up without
For general inquiries about our open source software and database management tools, please send us your question and someone will contact you.