Percona XtraBackup 2.0.7

Milestone information

Project:
Percona XtraBackup
Series:
2.0
Version:
2.0.7
Released:
2013-05-06  
Registrant:
Alexey Kopytov
Release registered:
2013-05-07
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
1 Alexey Bychko, 10 Alexey Kopytov, 5 Ignacio Nin, 2 Laurynas Biveinis, 6 Sergei Glushchenko
Blueprints:
1 Implemented
Bugs:
24 Fix Released

Download files for this release

File Description Downloads

Release notes 

Percona is glad to announce the release of Percona XtraBackup 2.0.7 for MySQL on May 6, 2013. Downloads are available from our download site here and Percona Software Repositories. Percona XtraBackup is the world’s only open-source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases.

This release is the current GA (Generally Available) stable release in the 2.0 series.

New Features:

    This version of Percona XtraBackup has implemented full support for new MySQL 5.6 features (GTID, remote/transportable tablespaces, separate undo tablespace, 5.6-style buffer pool dump files).
    Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6 buffer pool dumps can be produced and loaded for faster server warmup after the start. This feature is similar to the Dump/Restore of the Buffer Pool in Percona Server. MySQL 5.6 buffer pool dump is copied into backup directory during the backup stage. During the copy back stage (restore) it is copied back to data directory. After the backup is restored buffer pool dump can be loaded by the server either automatically on startup or on demand.
    Time interval between checks done by log copying thread is now configurable by innobackupex –log-copy-interval. Making the interval configurable allows to reduce the time between checks which can prevent XtraBackup failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
    Percona XtraBackup now stores the GTID value in the xtrabackup_binlog_info when doing the backup of MySQL and Percona Server 5.6 with the GTID mode enabled. Example of how this information can be used to create/restore a slave can be found in this blogpost.
    Percona XtraBackup option xtrabackup –export now supports transportable tablespaces introduced in MySQL 5.6. This option can be used to produce 5.6-style metadata files, that can be imported by ALTER TABLE IMPORT TABLESPACE on MySQL and Percona Server 5.6 as described in Exporting and Importing Tables guide.

Bugs Fixed:

    xtrabackup_56 binary was present in rpm and deb packages, but it was missing from the source .tar.gz package. Fixed by adding the missing binary to .tar.gz as well. Bug fixed #1158948.
    innobackupex could crash when taking the 5.6 backup due to linking the wrong SSL library. Bug fixed #1168540.
    Percona XtraBackup would crash when preparing the 5.6 backup with partitioned tables. Bug fixed #1169169.
    Tables that were dropped between taking a full backup and an incremental one were present in the full backup directory, and were not removed when incremental backups has been merged. Fixed by removing files corresponding to tables that are missing in the incremental backup directory. Bug fixed #856400.
    Percona XtraBackup would leave stale xtrabackup_tmp* files in the datadir after applying incremental backups. Bug fixed #1079135.
    Fixed couple of warnings found in innobackupex when all warnings have been made FATAL. Bug fixed #1116177.
    If there are thousands of tables and slow IO then XtraBackup can spend a lot of time opening all the tablespaces. Optimization has been implemented and XtraBackup now avoids loading non-relevant tablespaces when partial backup is being taken which speeds up the backup process. Bug fixed #1130145.
    Percona XtraBackup didn’t initialize per-thread data in the log copying thread which could cause XtraBackup to crash. Bug fixed #1166888.
    Package dependency has been changed from abstract mysql to real /usr/bin/mysql file, because rpm packages from Oracle no longer satisfied mysql dependency which is required by the XtraBackup rpms. Bug fixed #1095972.
    Percona XtraBackup would fail when preparing the MySQL 5.6 backup if the log files were bigger than 4G on the source server. Bug fixed #1164979.
    Due to different implementation in MySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error or diagnostic messages are never printed by xtrabackup_56. Bug fixed #1169971.
    innobackupex would still run with FLUSH TABLES WITH READ LOCK even if xtrabackup would fail when copying logs. Fixed by terminating xtrabackup process immediately on log copying failure. Bug fixed #1170806.
    innobackupex would fail if the SQL_MODE was set to ANSI_QUOTES. Bug fixed #945161.
    Missing space_id from *.ibd.meta would lead to assertion. Fixed by replacing the assertion with the error message. Bug fixed #1112224.
    Fixed the typo in the innobackupex error output. Bug fixed #1157225.
    When building from source innodb56 target didn’t have an option to disable DTrace like innodb55 has. Fixed by adding -DENABLE_DTRACE=OFF build option for innodb56 as well. Bug fixed #1169509.
    innobackupex wasn’t handling the innodb_data_file_path option which could cause backup to fail. Bug fixed #1169726.
    For the Debian and the Linux binaries, the --version message which should include the revision was showing “undefined”. Bug fixed #1171721.
    Redundant code has been removed from xtrabackup.cc. Bug fixed #1162765.

Other bug fixes: bug fixed #1158154, bug fixed #1170340, bug fixed #1088309, bug fixed #1088307.

Release notes with all the bugfixes for Percona XtraBackup 2.0.7 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

Changelog 

This release does not have a changelog.

1 blueprint and 24 bugs targeted

Blueprint Priority Assignee Delivery
Full MySQL 5.6 support Full MySQL 5.6 support 5 Essential   11 Implemented
Bug report Importance Assignee Status
1158948 #1158948 percona-xtrabackup-2.0.6-521.tar.gz does not contain xtrabackup_56: 2 Critical Ignacio Nin  10 Fix Released
1168540 #1168540 New tarball 2.0.6-523 for xtrabackup_56 has error: "xtrabackup_56: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory " 2 Critical Ignacio Nin  10 Fix Released
1169169 #1169169 xtrabackup_56 crashes when preparing a backup with partitioned tables 2 Critical Alexey Kopytov  10 Fix Released
856400 #856400 Remove dropped tables from a full backup when merging an incremental one 3 High Sergei Glushchenko  10 Fix Released
1079135 #1079135 stale xtrabackup_tmp* files after applying incremental backups 3 High Sergei Glushchenko  10 Fix Released
1116177 #1116177 Fix warnings reported by "use warnings FATAL => 'all'" 3 High Alexey Kopytov  10 Fix Released
1125993 #1125993 This is a request to make the time interval between checks done by log copying thread configurable 3 High Sergei Glushchenko  10 Fix Released
1130145 #1130145 If there are thousands of tables and slow IO then Xtrabackup can spend a lot of time opening all the tablespaces 3 High Sergei Glushchenko  10 Fix Released
1166888 #1166888 XtraBackup segfaults after period of time 3 High Alexey Kopytov  10 Fix Released
1088307 #1088307 debian/copyright not in new machine-readable format 4 Medium Ignacio Nin  10 Fix Released
1088309 #1088309 debian/rules is pre dh7 ruleset 4 Medium Ignacio Nin  10 Fix Released
1095972 #1095972 rpm dependency on "mysql" no longer satisfied by Oracle MySQL 5.5.29 packages 4 Medium Alexey Bychko  10 Fix Released
1164979 #1164979 xtrabackup_56 can fail on prepare if log files > 4G used on source server 4 Medium Laurynas Biveinis  10 Fix Released
1169971 #1169971 Lost InnoDB messages in xtrabackup_56 4 Medium Alexey Kopytov  10 Fix Released
1170340 #1170340 require_partitioning in test/inc/ib_part.sh does not work with 5.6 4 Medium Alexey Kopytov  10 Fix Released
1170806 #1170806 innobackupex continuing with FTWRL even when xtrabackup failed 4 Medium Alexey Kopytov  10 Fix Released
945161 #945161 innobackupex fails if SQL_MODE=ANSI_QUOTES 5 Low Alexey Kopytov  10 Fix Released
1112224 #1112224 Missing space_id from *.ibd.meta Leads to Assertion 5 Low Sergei Glushchenko  10 Fix Released
1157225 #1157225 typo from innobackupex when using --tables-file: "registerd" should "registered" 5 Low Alexey Kopytov  10 Fix Released
1169509 #1169509 innodb56 target also needs -DENABLE_DTRACE=OFF like innodb55 one 5 Low Alexey Kopytov  10 Fix Released
1169726 #1169726 innodb_data_file_path is handled by innobackupex incorrectly 5 Low Sergei Glushchenko  10 Fix Released
1171721 #1171721 Revision undefined in --version in some platforms 5 Low Ignacio Nin  10 Fix Released
1162765 #1162765 Possible merge issue in xtrabackup.cc 6 Wishlist Alexey Kopytov  10 Fix Released
1158154 #1158154 Suboptimal debug code in mem_init_buf() and mem_erase_buf() 1 Undecided Laurynas Biveinis  10 Fix Released
This milestone contains Public information
Everyone can see this information.