Percona XtraBackup 1.6.3Rodrigo Gadea
This release is purely composed of bug fixes and is the current stable release of Percona Xtrabackup.
innodb_file_per_table server option is being used and DDL operations,
DROP/CREATE the_same_table or
ALTER statements on InnoDB tables are executed while taking a backup, an upgrade to XtraBackup 1.6.3 is strongly recommended. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is also recommended.
All of Percona’s software is open-source and free, all the details of the release and its development process can be found in the 1.6.3 milestone at Launchpad.
Streaming backups did not work for compressed InnoDB tables due to missing support for compressed pages in
tar4ibd. Bug Fixed: #665210 (Alexey Kopytov).
XtraBackup failed when
innodb_flush_methodin the server configuration file was set to
ALL_O_DIRECT. Bug Fixed: #759225 (Alexey Kopytov).
Due to a regression introduced in XtraBackup 1.6.2,
innobackupex --copy-backdid not work if the
xtrabackupbinary was not specified explicitly with the
--ibbackupoption. Bug Fixed: #817132 (Alexey Kopytov).
--slave-infooption now works correctly with
--incrementalis also specified. Bug Fixed: #834657 (Alexey Kopytov).
tar4ibdcould fail with an error when processing doublewrite pages. Bug Fixed: #810269 (Alexey Kopytov).
- Unsupported command line options could cause a tar4ibd crash. Such options have been removed. Bug Fixed: #677279 (Alexey Kopytov).
Executing DDL operations,
ALTERstatements on InnoDB tables while taking a backup could lead to a
xtrabackupfailure due to a tablespace ID mismatch when using per-table tablespaces. Note that this fix may not work correctly with MySQL 5.5 or Percona Server 5.5 prior to version 5.5.11. 5.1 releases from 5.1.49 or higher have been confirmed not to be affected. If the
innodb_file_per_tableoption is being used, an upgrade to XtraBackup 1.6.3 isstrongly recommended. Under this scenario, if the server version is prior to 5.5.11 in 5.5 series or prior to 5.1.49 in 5.1 series, a server upgrade is alsorecommended. Bug Fixed: #722638 (Alexey Kopytov).
For more information, please see the following links: