September 20, 2014

Percona XtraBackup 2.1.7 is now available

Percona XtraBackup for MySQL Percona is glad to announce the release of Percona XtraBackup 2.1.7 on January 24th, 2014. 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.1 series. Percona XtraBackup is an open source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases. Percona XtraBackup is an open source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases.

New Features

  • Percona XtraBackup has now been rebased on MySQL versions 5.1.73, 5.5.35, 5.6.15 and Percona Server versions 5.1.73-rel14.11 and 5.5.35-rel33.0.

Bugs Fixed

  • After being rebased on MySQL 5.6.11 Percona XtraBackup has been affected by the upstream bug #69780. Fixed by rebasing Percona XtraBackup on MySQL 5.6.15 which contains a fix for the upstream bug. Bug fixed #1203669.
  • Backup directory would need to be specified even for running the innobackupex with --help and --version options. Bug fixed #1223716.
  • When creating an incremental backup with the changed page tracking feature available in Percona Server, innobackupex would fail if the server had the ANSI_QUOTES SQL mode enabled. Bug fixed #1248331.
  • When innobackupex --galera-info is specified and Percona XtraDB Cluster is using GTID replication (version 5.6 only), innobackupex will execute FLUSH BINARY LOGS and then carry the current binary log as indicated in SHOW MASTER STATUS into the backup set. Bug fixed #1250375.
  • Percona XtraBackup did not roll back prepared XA transactions when applying the log. Which was a regression introduced with the original port of Percona XtraBackup patches to 5.6. Fixed by restoring code that has been lost in the port. Bug fixed #1254227.
  • Percona XtraBackup now uses libgcrypt built in randomization functions for setting the Initialization Vector. Bug fixed #1255300.
  • xtrabackup_56 didn’t support ALL_O_DIRECT option for innodb_flush_method in Percona Server 5.6. Bug fixed #1261877.

Other bugs fixed: #1255019, #1268325, #1265759, #1269694, #1271501.

Release notes with all the bugfixes for Percona XtraBackup 2.1.7 are available in our online documentation. All of Percona‘s software is open source and free, all the details of the release can be found in the 2.1.7 milestone at Launchpad. Bugs can be reported on the launchpad bug tracker.

Comments

  1. Anh says:

    Hi,

    Can you show me any article that helps me to restore a single database (not just some tables) from a full mysql backup. Have been searching for this but got nothing. Overall, the main reason I am not sure about trying Percona products is the lack of documentation.

  2. Hrvoje Matijakovic says:
  3. Anh says:

    Hi Hrvoje,

    Regarding the article you referred, I see

    It can also be done by copying back the prepared backup to a “clean” datadir (in that case, make sure to include the mysql database).

    Can I copy a single database, i.e., a subfolder in /var/lib/mysql to the datadir or I can only copy the whole datadir /var/lib/mysql.

  4. shamim says:

    so the new version is going to take care of the above problem. Instead of doing imports of individual tables can we restore the database with 1 command on a existing server and not a new install?

  5. Hrvoje Matijakovic says:

    @Anh
    You should just copy the /var/lib/mysql/mysql directory to the directory in which you made the partial backup and already run –aply-log –export (ie, /data/backups/2014-01-25-15-17-16). Copying the entire data directory would cause the backups to become inconsistent.
    Regarding the lack of documentation, can you please report documentation bug(s) here (https://bugs.launchpad.net/percona-xtrabackup/+filebug) and I’ll make sure to improve the docs.

    @shamim
    No, this version doesn’t support one-command database restore to the existing server.

  6. Anh says:

    Thanks Hrvoje.

Speak Your Mind

*