Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.6

Milestone information

Project:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Series:
2.2
Version:
2.2.6
Released:
2014-11-03  
Registrant:
Hrvoje Matijakovic
Release registered:
2014-11-04
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:
17 Alexey Kopytov, 9 Sergei Glushchenko
Blueprints:
1 Implemented
Bugs:
25 Fix Released

Download files for this release

File Description Downloads

Release notes 

Changelog 

View the full changelog

New Features

Percona XtraBackup now reads server options from SHOW VARIABLES rather than my.cnf configuration file.

Percona XtraBackup now has more verbose output during initial table scan (it will now print a diagnostic message before performing a tablespace scan, which may take a long time on systems with large numbers of tablespaces) and before starting a backup/apply-log/copy-back operation in innobackupex (it will now print a diagnostic message with a timestamp to make it easier for users to get duration of the operation.)

Bugs Fixed

innobackupex didn’t take the default datadir, which caused backups to fail if the datadir wasn’t specified in the my.cnf configuration file. Bug fixed #936934.

innobackupex will now fail with an error when innobackupex --slave-info is used on a multi-threaded non-GTID slave, because Exec_Master_Log_Pos cannot be trusted for a multi-threaded slave. Bug fixed #1372679.

InnoDB log scanning failure (bug #60788) would cause backups to fail. Fixed by porting the fix from MySQL 5.7. Bug fixed #1375383.

Options innobackupex --apply-log and innobackupex --decompress weren’t marked as mutually exclusive, ie. if they were both specified, only innobackupex --decompress would work, which could lead to MySQL instance being started with an unprepared backup. Fixed by making mutually exclusive categories of options: 1. innobackupex --decompress, innobackupex --decrypt; 2. innobackupex --copy-back; 3. innobackupex --move-back; 4. innobackupex --apply-log. Bug fixed #1376874.

innobackupex wasn’t creating directories specified in innodb_data_home_dir and innodb_log_group_home_dir when innobackupex --copy-back option was used. Bug fixed #1382347.

Percona XtraBackup now supports all option modifiers supported by upstream MySQL: skip, disable, enable, maximum, loose. Bug fixed #664128.

Percona XtraBackup would fail to perform a full backup on Percona Server 5.5 if innodb_log_file_size variable wasn’t set in the [mysqld] section of my.cnf. Bug fixed #1334062.

Other bugs fixed: #1379905, #1386013, #1072695, #1375241, #1182841, and #1343722.

1 blueprint and 25 bugs targeted

Blueprint Priority Assignee Delivery
Read server options from SHOW VARIABLES rather than my.cnf Read server options from SHOW VARIABLES rather than my.cnf 4 High Alexey Kopytov  11 Implemented
Bug report Importance Assignee Status
936934 #936934 innobackupex don't take the default datadir 4 Medium Alexey Kopytov  10 Fix Released
936934 #936934 innobackupex don't take the default datadir 4 Medium Alexey Kopytov  10 Fix Released
1372679 #1372679 innobackupex --slave-info doesn't handle slave_parallel_workers>0 4 Medium Alexey Kopytov  10 Fix Released
1375383 #1375383 InnoDB log scanning failure results in SST failure 4 Medium Sergei Glushchenko  10 Fix Released
1375383 #1375383 InnoDB log scanning failure results in SST failure 4 Medium Sergei Glushchenko  10 Fix Released
1376874 #1376874 --apply-log and --decompress aren't marked as mutually exclusive in the documentation 4 Medium Sergei Glushchenko  10 Fix Released
1376874 #1376874 --apply-log and --decompress aren't marked as mutually exclusive in the documentation 4 Medium Sergei Glushchenko  10 Fix Released
1379905 #1379905 Regressions from the fix for bug #1375383 on 32-bit platforms 4 Medium Sergei Glushchenko  10 Fix Released
1379905 #1379905 Regressions from the fix for bug #1375383 on 32-bit platforms 4 Medium Sergei Glushchenko  10 Fix Released
1382347 #1382347 Include innodb_log_group_home_dir and innodb_undo_directory as special variables supported by sst_special_dirs 4 Medium Sergei Glushchenko  10 Fix Released
1386013 #1386013 innodb_data_home_dir support is buggy (PXB 2.2 regression) 4 Medium Sergei Glushchenko  10 Fix Released
1386013 #1386013 innodb_data_home_dir support is buggy (PXB 2.2 regression) 4 Medium Sergei Glushchenko  10 Fix Released
664128 #664128 xtrabackup does not support "--loose-" options 5 Low Alexey Kopytov  10 Fix Released
664128 #664128 xtrabackup does not support "--loose-" options 5 Low Alexey Kopytov  10 Fix Released
1072695 #1072695 XtraBackup test framework force to use original my.cnf during prepare 5 Low Alexey Kopytov  10 Fix Released
1072695 #1072695 XtraBackup test framework force to use original my.cnf during prepare 5 Low Alexey Kopytov  10 Fix Released
1334062 #1334062 Xtrabackup 2.2.3 fails to perform a full backup on PS 5.5 if innodb_log_file_size on the [mysqld] section of my.cnf is not set 5 Low Alexey Kopytov  10 Fix Released
1334062 #1334062 Xtrabackup 2.2.3 fails to perform a full backup on PS 5.5 if innodb_log_file_size on the [mysqld] section of my.cnf is not set 5 Low Alexey Kopytov  10 Fix Released
1375241 #1375241 innobackupex does not (properly) check for file open errors in some cases 5 Low Alexey Kopytov  10 Fix Released
1375241 #1375241 innobackupex does not (properly) check for file open errors in some cases 5 Low Alexey Kopytov  10 Fix Released
369913 #369913 Feature Request: more verbose output during initial table scan 6 Wishlist Alexey Kopytov  10 Fix Released
1182841 #1182841 Traceback in innobackupex 6 Wishlist Alexey Kopytov  10 Fix Released
1182841 #1182841 Traceback in innobackupex 6 Wishlist Alexey Kopytov  10 Fix Released
1343722 #1343722 Too easy to backup wrong datadir with multiple instances 6 Wishlist Alexey Kopytov  10 Fix Released
1343722 #1343722 Too easy to backup wrong datadir with multiple instances 6 Wishlist Alexey Kopytov  10 Fix Released
This milestone contains Public information
Everyone can see this information.