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

Milestone information

Project:
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Series:
2.4
Version:
2.4.3
Released:
2016-05-23  
Registrant:
Hrvoje Matijakovic
Release registered:
2016-05-23
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:
9 Sergei Glushchenko
Blueprints:
1 Implemented
Bugs:
8 Fix Released

Download files for this release

File Description Downloads

Release notes 

Changelog 

View the full changelog

New features
Percona XtraBackup has implemented new xtrabackup --reencrypt-for-server-id option. Using this option allows users to start the server instance with different server_id from the one the encrypted backup was taken from, like a replication slave or a galera node. When this option is used, xtrabackup will, as a prepare step, generate a new master key with ID based on the new server_id, store it into keyring file and re-encrypt the tablespace keys inside of tablespace headers.
Bugs Fixed
Running DDL statements on Percona Server 5.7 during the backup process could in some cases lead to failure while preparing the backup. Bug fixed #1555626.

MySQL 5.7 can sometimes skip redo logging when creating an index. If such ALTER TABLE is being issued during the backup, the backup would be inconsistent. xtrabackup will now abort with error message if such ALTER TABLE has been done during the backup. Bug fixed #1582345.

.ibd files for remote tablespaces were not copied back to original location pointed by the .isl files. Bug fixed #1555423.

When called with insufficient parameters, like specifying the empty --defaults-file option, Percona XtraBackup could crash. Bug fixed #1566228.

Documentation states that the default value for --ftwrl-wait-query-type is all, however it was update. Changed the default value to reflect the documentation. Bug fixed #1566315.

When --keyring-file-data option was specified, but no keyring file was found, xtrabackup would create an empty one instead of reporting an error. Bug fixed #1578607.

If ALTER INSTANCE ROTATE INNODB MASTER KEY was run at same time when xtrabackup --backup was bootstrapping it could catch a moment when the key was not written into the keyring file yet and xtrabackup would overwrite the keyring with the old copy of a keyring, so the new key would be lost. Bug fixed #1582601.

Output of xtrabackup --slave-info option was missing an apostrophe. Bug fixed #1573371.

1 blueprint and 8 bugs targeted

Blueprint Priority Assignee Delivery
Add option to re-encrypt tablespace keys for given server-id Add option to re-encrypt tablespace keys for given server-id 4 High Sergei Glushchenko  11 Implemented
Bug report Importance Assignee Status
1555626 #1555626 Backup corrupted for PS 5.7 when DDL statements running 2 Critical Sergei Glushchenko  10 Fix Released
1582345 #1582345 Handle MLOG_INDEX_LOAD during the backup 2 Critical Sergei Glushchenko  10 Fix Released
1555423 #1555423 Fix for 1322658 not ported to 2.3 and 2.4 of Xtrabackup 3 High Sergei Glushchenko  10 Fix Released
1566228 #1566228 XB crashes with insufficient param. 3 High Sergei Glushchenko  10 Fix Released
1566315 #1566315 percona xtrabackup not reflecting --ftwrl-wait-timeout parameter value 3 High Sergei Glushchenko  10 Fix Released
1578607 #1578607 xtrabackup should not create keyring file if there is no one found at specified path 3 High Sergei Glushchenko  10 Fix Released
1582601 #1582601 Getting "Can't find master key from keyring error" after starting full backup 3 High Sergei Glushchenko  10 Fix Released
1573371 #1573371 xtrabackup 2.4.2 --slave-info miss apostrophe 5 Low Sergei Glushchenko  10 Fix Released
This milestone contains Public information
Everyone can see this information.