New Features
Percona XtraBackup has been rebased on MySQL 5.6.21.
Bugs Fixed
The fix for bug #1079700 introduced a problem for users with huge numbers of InnoDB tablespaces, and the workaround of raising the open files limits didn’t work in all cases due to a limitation in the Linux kernel. A new innobackupex --close-files option has been implemented to close the file handles once they are no longer accessed. NOTE: Using this option may result in a broken backup if DDL is performed on InnoDB tables during the backup procedure. Bug fixed #1222062.
Fix for bug #1206309 introduced a regression in Percona XtraBackup 2.2.0 which caused Percona XtraBackup to fail to copy redo logs in random cases. Bug fixed #1365835.
innobackupex --galera-info didn’t copy the last binlog file when it was taking a backup from server where backup locks are supported. Bug fixed #1368577.
xtrabackup binary would accept arguments that were not options, which could lead to unexpected results. Bug fixed #1367377.
If innobackupex is run against MySQL 5.1 with built-in InnoDB, it will now suggest using Percona XtraBackup 2.0 or upgrading to InnoDB plugin, rather than just failing with the generic unsupported server version message. Bug fixed #1335101.
Using the (deprecated) log parameter in mysqld section would cause backups to fail. Bug fixed #1347698.
Percona XtraBackup now uses MySQL code to get the stack trace in case Percona XtraBackup crashes with a segmentation fault or an assertion failure. Bug fixed #766305.
Attempt to use any of the following options without the innobackupex --incremental option now fails with an error message rather than creates a full backup: innobackupex --incremental-lsn, innobackupex --incremental-basedir, innobackupex --incremental-history-name, innobackupex --incremental-history-uuid. Bug fixed #1213778.
Other bugs fixed: #1367613, #1368574, #1370462, #1371441, #1373429, #1373984, and #1265070.
