Percona XtraBackup 2.1.7

Percona is glad to announce the release of Percona XtraBackup 2.1.7 on January 24th 2014. Downloads are available from our download site here and Percona Software Repositories.

This release is the current GA (Generally Available) stable release in the 2.1 series.

New Features

Percona XtraBackup has now been rebased on MySQL versions 5.1.73, 5.5.35, 5.6.15 and Percona Server versions 5.1.73-rel14.11 and 5.5.35-rel33.0.

Bugs Fixed

After being rebased on MySQL 5.6.11 Percona XtraBackup has been affected by the upstream bug #69780. Fixed by rebasing Percona XtraBackup on MySQL 5.6.15 which contains a fix for the upstream bug. Bug fixed #1203669.

Backup directory would need to be specified even for running the innobackupex with innobackupex --help and innobackupex --version options. Bug fixed #1223716.

When creating an incremental backup with the changed page tracking feature available in Percona Server, innobackupex would fail if the server had the ANSI_QUOTES SQL mode enabled. Bug fixed #1248331.

When innobackupex --galera-info is specified and Percona XtraDB Cluster is using GTID replication (version 5.6 only), innobackupex will execute FLUSH BINARY LOGS and then carry the current binary log as indicated in SHOW MASTER STATUS into the backup set. Bug fixed #1250375.

Percona XtraBackup did not roll back prepared XA transactions when applying the log. Which was a regression introduced with the original port of Percona XtraBackup patches to 5.6. Fixed by restoring code that has been lost in the port. Bug fixed #1254227.

Percona XtraBackup now uses libgcrypt built in randomization functions for setting the Initialization Vector. Bug fixed #1255300.

xtrabackup_56 didn’t support ALL_O_DIRECT option for innodb_flush_method in Percona Server 5.6. Bug fixed #1261877.

Other bugs fixed: #1255019, #1268325, #1265759, #1269694, #1271501.