Percona is glad to announce the release of Percona XtraBackup 2.2.2-beta1 on May 8th 2014. Downloads are available from our download site here. This BETA release, will be available in our Debian experimental and CentOS testing repositories.
This is a BETA quality release and it is not intended for production. If you want a high quality, Generally Available release, the current Stable version should be used (Percona XtraBackup 2.1.9 in the 2.1 series at the time of writing).
- 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
ulimitsettings. Bug fixed #1183793.
- If a remote InnoDB tablespace got
ALTERed during the backup, an attempt to prepare such a backup later would lead to Percona XtraBackup crash. Bug fixed #1291299.
- Code in both
xtrabackup, that was supposed to make sure no child processes are left running in case
innobackupexgot killed or failed with an error, relied on the fact the
SIGINTsignals were not blocked by the
xtrabackupprocess. However, both
SIGINTmight 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
SIGTERMin innobackupex and
SIGINTin xtrabackup auto-termination with
SIGKILL. Bug fixed #1294782.
Release notes with all the bugfixes for Percona XtraBackup 2.2.2 are available in our online documentation. All of Percona‘s software is open source and free, all the details of the release can be found in the 2.2.2 milestone at Launchpad. Bugs can be reported on the launchpad bug tracker.