Percona XtraBackup 2.4.3¶
This release is the GA (Generally Available) stable release in the 2.4 series.
Percona XtraBackup has implemented new
xtrabackup --reencrypt-for-server-id option. Using this option
allows users to start the server instance with different
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
store it into keyring file and re-encrypt the tablespace keys inside of
Running DDL statements on Percona Server for MySQL 5.7 during the backup process could in some cases lead to failure while preparing the backup. Bug fixed PXB-247.
MySQL 5.7 can sometimes skip redo logging when creating an index. If such
ALTER TABLEis being issued during the backup, the backup would be inconsistent. xtrabackup will now abort with error message if such
ALTER TABLEhas been done during the backup. Bug fixed PXB-249.
.ibdfiles for remote tablespaces were not copied back to original location pointed by the .isl files. Bug fixed PXB-466.
When called with insufficient parameters, like specifying the empty
xtrabackup --defaults-fileoption, Percona XtraBackup could crash. Bug fixed PXB-471.
Documentation states that the default value for
all, however it was
update. Changed the default value to reflect the documentation. Bug fixed PXB-472.
xtrabackup --keyring-file-dataoption was specified, but no keyring file was found, xtrabackup would create an empty one instead of reporting an error. Bug fixed PXB-476.
ALTER INSTANCE ROTATE INNODB MASTER KEYwas run at same time when
xtrabackup --backupwas 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 PXB-478.
xtrabackup --slave-infooption was missing an apostrophe. Bug fixed PXB-940.