Percona XtraBackup 1.6.3

Percona is glad to announce the release of Percona XtraBackup 1.6.3 on 22 September, 2011 (Downloads are available here and from the Percona Software Repositories).

This release is purely composed of bug fixes and is the current stable release of Percona XtraBackup.

If the innodb_file_per_table server option is been used and DDL operations, TRUNCATE TABLE, DROP/CREATE the_same_table or ALTER statements on InnoDB tables are executed while taking a backup, an upgrade to Percona 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.

Bugs Fixed

  • Streaming backups did not work for compressed InnoDB tables due to missing support for compressed pages in tar4ibd. Bug Fixed: #665210 (Alexey Kopytov).
  • Percona XtraBackup failed when innodb_flush_method in the server configuration file was set to ALL_O_DIRECT. Bug Fixed: #759225 (Alexey Kopytov).
  • Due to a regression introduced in Percona XtraBackup 1.6.2, innobackupex –copy-back did not work if the xtrabackup binary was not specified explicitly with the --ibbackup option. Bug Fixed: #817132 (Alexey Kopytov).
  • The --slave-info option now works correctly with --safe-slave-backup when either --no-lock or --incremental is also specified. Bug Fixed: #834657 (Alexey Kopytov).
  • tar4ibd could 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, TRUNCATE TABLE, DROP/CREATE the_same_table or ALTER statements on InnoDB tables while taking a backup could lead to a xtrabackup failure 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_table option is been used, an upgrade to Percona 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. Bug Fixed: #722638 (Alexey Kopytov).

Other Changes

Percona XtraBackup
Call Us
+1-888-316-9775 (USA - Sales)
+1-208-473-2904 (USA - Sales)
+44-208-133-0309 (UK - Sales)
0-800-051-8984 (UK - Sales)
0-800-181-0665 (GER - Sales)
+1-877-862-4316 (Emergency)
+1-855-55TRAIN (Training)
+1-925-271-5054 (Training)

Table Of Contents

Previous topic

Percona XtraBackup 1.6.2

Next topic

Percona XtraBackup 1.6.4

This Page



© Copyright 2009-2014, Percona LLC and/or its affiliates.
Except where otherwise noted, this documentation is licensed under the following license:
CC Attribution-ShareAlike 2.0 Generic
Created using Sphinx 1.2.2.
This documentation is developed in Launchpad as part of the Percona XtraBackup source code.
If you spotted innacuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.
]]>