Percona XtraBackup 1.6.7¶
This release is purely composed of bug fixes and is the current stable release of Percona XtraBackup.
xtrabackup_binary was not included in tar archive when streaming, instead it
was written to the current directory. This could lead to a wrong xtrabackup
binary being used when preparing backups created with the
xtrabackup --remote-host options. Bugs fixed
#723318 and #787988 (Stewart Smith).
FLUSH TABLES WITH READ LOCK was not used when creating incremental backups,
which could lead to inconsistent backups when updates to non-InnoDB tables or
DDL statements on any tables occurred during the backup process. Bug fixed
#771981 (Alexey Kopytov).
innobackupex --safe-slave-backup was resulting in incorrect
binlog info, because in some cases innobackupex confused the response from SHOW
SLAVE STATUS with the one from SHOW MASTER STATUS. Bug fixed #977101
innodb_data_file_path was not written to
backup-my.cnf, this was a
regression introduced in Percona XtraBackup 1.6.5. Bug fixed #983685
Fixed spurious test suite failures with grep 2.10. Bug fixed #996483 (Alexey Kopytov).
When innobackupex was running with
innobackupex --apply-log, it was
reading configuration from the server configuration file instead of
backup-my.cnf in backup directory. Bug fixed #996493 (Sergei
innobackupex could copy files to a wrong directory when merging an incremental backup to a full one. Bug fixed #1002688 (Alexey Kopytov).
Other bugs fixed: bug #1021954 (Hrvoje Matijakovic).