Percona XtraBackup 2.1.9¶
This release is the current GA (Generally Available) stable release in the 2.1 series.
Percona XtraBackup has now been rebased on MySQL 5.6.17.
Percona XtraBackup package is now available for Ubuntu 14.04.
Percona XtraBackup couldn’t be built with Bison 3.0. Bug fixed #1262439.
The xtrabackup binaries now recognize a new
open_files_limit. The effect is the same as for the server: it changes
the maximum number of file descriptors available to the xtrabackup process. The
actual limit depends on the platform and
ulimit settings. Bug fixed
If a remote InnoDB tablespace got CREATEd or ALTERed during the backup, an attempt to prepare such a backup later would lead to Percona XtraBackup crash. Bug fixed #1291299.
Code in both innobackupex and xtrabackup, that was supposed to make sure no
child processes are left running in case innobackupex got killed or failed
with an error, relied on the fact the
SIGINT signals were
not blocked by the xtrabackup process. However, both
might be blocked by the process that had invoked innobackupex, for example, by
the Percona XtraDB Cluster server processes doing an SST, in which case they
were also blocked by the xtrabackup process, since the signal mask is inherited
by child processes. Fixed by replacing
SIGTERM in innobackupex and
SIGINT in xtrabackup auto-termination with
SIGKILL. Bug fixed
A new table flag in the InnoDB data dictionary, introduced in MySQL 5.6.16,
wasn’t recognized by Percona XtraBackup which lead to
InnoDB: in InnoDB data
dictionary has unknown flags 50. warnings. Fixed by rebasing Percona XtraBackup on MySQL 5.6.17. Bug fixed #1302882.
All of Percona’s software is open-source and free, all the details of the release can be found in the 2.1.9 milestone <https://launchpad.net/percona-xtrabackup/+milestone/2.1.9> at Launchpad.