Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.0.6
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 1 Alexey Bychko, 12 Alexey Kopytov, 5 Laurynas Biveinis, 1 Sergei Glushchenko
- Blueprints:
- 2 Implemented
- Bugs:
- 17 Fix Released
Download files for this release
Release notes
Percona is glad to announce the release of Percona XtraBackup 2.0.6 on March 20, 2013. Downloads are available from our download site here and Percona Software Repositories.
This release is the current GA (Generally Available) stable release in the 2.0 series.
New Features:
XtraBackup has implemented basic support for MySQL 5.6, Percona Server 5.6 and MariaDB 10.0. Basic support means that these versions are are recognized by XtraBackup, and that backup/restore works as long as no 5.6-specific features are used (such as GTID, remote/
Bugs Fixed:
Individual InnoDB tablespaces with size less than 1MB were extended to 1MB on the backup prepare operation. This led to a large increase in disk usage in cases when there are many small InnoDB tablespaces. Bug fixed #950334 (Daniel Frett, Alexey Kopytov).
Fixed the issue that caused databases corresponding to inaccessible datadir subdirectories to be ignored by XtraBackup without warning or error messages. This was happening because InnoDB code silently ignored datadir subdirectories it could not open. Bug fixed #664986 (Alexey Kopytov).
Under some circumstances XtraBackup could fail to copy a tablespace with a high --parallel option value and a low innodb_open_files value. Bug fixed #870119 (Alexey Kopytov).
Fix for the bug #711166 introduced a regression that caused individual partition backups to fail when used with --include option in innobackupex or the --tables option in xtrabackup. Bug fixed #1130627 (Alexey Kopytov).
innobackupex didn’t add the file-per-table setting for table-independent backups. Fixed by making XtraBackup auto-enable innodb_
Under some circumstances XtraBackup could fail on a backup prepare with innodb_
innobackupex did not pass the --tmpdir option to the xtrabackup binary resulting in the server’s tmpdir always being used for temporary files. Bug fixed #1085099 (Alexey Kopytov).
XtraBackup has improved the error reporting for unrecognized server versions. Bug fixed #1087219 (Alexey Kopytov).
Fixed the missing rpm dependency for Perl Time::HiRes package that caused innobackupex to fail on minimal CentOS installations. Bug fixed #1121573 (Alexey Bychko).
innobackupex would fail when --no-lock and --rsync were used in conjunction. Bug fixed #1123335 (Sergei Glushchenko).
Fix for the bug #1055989 introduced a regression that caused xtrabackup_pid file to remain in the temporary dir after execution. Bug fixed #1114955 (Alexey Kopytov).
Unnecessary debug messages have been removed from the XtraBackup output. Bug fixed #1131084 (Alexey Kopytov).
Other bug fixes: bug fixed #1153334 (Alexey Kopytov), bug fixed #1098498 (Laurynas Biveinis), bug fixed #1132763 (Laurynas Biveinis), bug fixed #1142229 (Laurynas Biveinis), bug fixed #1130581 (Laurynas Biveinis).
Release notes with all the bugfixes for Percona XtraBackup 2.0.6 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.
Changelog
This release does not have a changelog.
2 blueprints and 17 bugs targeted
| Blueprint | Priority | Assignee | Delivery | |
|---|---|---|---|---|
| Basic 5.6 support | Basic 5.6 support | 5 Essential | Alexey Kopytov | 11 Implemented |
| Support building against MySQL/InnoDB 5.6 | Support building against MySQL/InnoDB 5.6 | 5 Essential | Laurynas Biveinis | 11 Implemented |
