Percona XtraBackup 2.2.12¶
This release is the current stable release in the 2.2 series.
Percona XtraBackup would segfault during the prepare phase of certain FTS pages. Bug fixed #1460138.
After the release of Percona XtraBackup 2.2.11, innobackupex issues a
FLUSH TABLEbefore running the
FLUSH TABLES WITH READ LOCK. While it will help the backups in some situation, it also implies that the
FLUSH TABLEwill be written to the binary log. On MariaDB 10.0 with GTID enabled, when backup was taken on the slave, this altered the GTID of that slave and Percona XtraBackup didn’t see the correct GTID anymore. Bug fixed #1466446 (Julien Pivotto).
RPM compilation of Percona XtraBackup was still requiring
bzr. Bug fixed #1466888 (Julien Pivotto).
Compiling Percona XtraBackup RPMs with
XB_VERSION_EXTRAoption would create an incorrect RPM version. Bug fixed #1467424 (Julien Pivotto).
Percona XtraBackup would complete successfully even when redo log wasn’t copied completely. This means that backup were considered successful even when they were corrupt. Bug fixed #1470847.
In rare cases when there are two or more tablespaces with the same ID in the data directory, xtrabackup picks up the first one by lexical order, which could lead to losing the correct table. Bug fixed #1475487.
Percona XtraBackup was missing
revision_idin binaries. Bug fixed #1394174.