XtraBackup Appears to Lock


I have read through the documentation, and have started to implement XtraBackups on our Percona configuration, the syntax I am using is:

innobackupex --user=bkpuser --password=backuppassword --no-timestamp /var/backups/new_backup5

The backup works fine, however in the log I can see:

180820 10:51:59 Finished backing up non-InnoDB tables and files
180820 10:51:59 Executing LOCK BINLOG FOR BACKUP…
180820 10:51:59 [00] Writing /var/backups/new_backup5/xtrabackup_binlog_info
180820 10:51:59 [00] …done
180820 10:51:59 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS…
xtrabackup: The latest check point (for incremental): ‘4281655043’
xtrabackup: Stopping log copying thread.
.180820 10:51:59 >> log scanned up to (4281655052)
180820 10:51:59 Executing UNLOCK BINLOG
180820 10:51:59 Executing UNLOCK TABLES
180820 10:51:59 All tables unlocked

Reading the documentation, we should have no locking during the backup, this is on a production system which we can’t lock. Am i missing a specific parameter or something?


Hello abarot, MyISAM and any other tables not using the InnoDB or XtraDB storage engines are locked for backup but only after it has finished with backing up InnoDB or XtraDB see here https://www.percona.com/doc/percona-xtrabackup/LATEST/how_xtrabackup_works.html