Percona XtraBackup 2.0.5

Percona is glad to announce the release of Percona XtraBackup 2.0.5 on January 18th, 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

New option --defaults-extra-file has been introduced. This option specifies from what extra file to read the default MySQL options before the standard defaults-file. It can be used to load the user/password combination for the dedicated backup user from a separate configuration file, to avoid storing it in the crontab or a script somewhere in the system.

Bugs Fixed

In case of streaming backups, innobackupex would resume the Percona XtraBackup process and then wait for it to finish before running UNLOCK TABLES. This caused database to be unnecessarily locked with FLUSH TABLES WITH READ LOCK. Innobackupex now waits only till log copying is finished to unlock the databases. Bug fixed #1055989 (Alexey Kopytov).

innobackupex error messages referencing the data directory have been extended to show the path of the data directory mentioned in the error message. Bug fixed #1089375 (Hartmut Holzgraefe).

Partitioned tables were not correctly handled by the --databases, --include, --tables-file options of innobackupex, and by the --tables and --tables-file options of Percona XtraBackup. Fixed by removing the partition suffix (#P#...) before doing filtering. Bug fixed #711166 (Sergei Glushchenko).

When built-in compression was used, Percona XtraBackup was doing unbuffered writes to the destination file or stream in very small chunks which in return caused inefficient I/O. Fixed by using a 1M buffer for output similar to the uncompressed backups. Bug fixed #1095249 (Alexey Kopytov).

Unnecessary long sleep() in innobackupex lead to FLUSH TABLES WITH READ LOCK taking too long. Fixed by replacing 2 seconds sleep interval with 100 milliseconds one. Bug fixed #1095551 (Sergei Glushchenko).

If innobackupex would crash it would leave the xtrabackup_suspended file on the filesystem. This could then cause innobackupex to think Percona XtraBackup has suspended itself the moment it started, and then when xtrabackup actually does suspend itself innobackupex would wait for it to end and wouldn’t re-remove the suspend_file, leading to a wait deadlock. Fixed by removing the stale xtrabackup_suspended file when innobackupex is started. Bug fixed #1007446 (George Ormond Lorch III).

innobackupex would fail to recognize MariaDB 5.2 and MariaDB 5.3. Fixed by augmenting version checks in innobackupex. Bug fixed #733665 (Daniël van Eeden, Alexey Kopytov).

Other bug fixes: bug fixed #924492 (Alexey Kopytov), bug fixed #1097158 (Alexey Kopytov), bug fixed #1081882 (Alexey Kopytov), bug fixed #1096584 (Alexey Kopytov),

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 2.0.4

Next topic

Percona XtraBackup 2.0.6

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.1.3.
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.
]]>