Percona XtraBackup 2.4.5¶
This release is the GA (Generally Available) stable release in the 2.4 series.
Percona XtraBackup now supports
SHA256passwords. Using the
SHA256algorithm requires either SSL encrypted connection, or using public key encryption for password exchange which is only available when both client and server are linked with OpenSSL.
Percona XtraBackup now supports Command Options for Secure Connections.
NOTE: Due to xbcrypt format changes, backups encrypted with this Percona XtraBackup version will not be recoverable by older versions.
Percona XtraBackup would crash while preparing the backup, during the shutdown, when master thread was performing checkpoint and purge thread was expecting that all other threads completed or were idle. Bug fixed #1618555.
Safe slave backup algorithm performed too short delays between retries which could cause backups to fail on a busy servers. Bug fixed #1624473.
Percona XtraBackup didn’t check the logblock checksums. Bug fixed #1633448.
Fixed new compilation warnings with GCC 6. Bug fixed #1641612.
xbcrypt was not setting the Initialization Vector (IV) correctly (and thus is was not using an IV). This was causing the same ciphertext to be generated across different runs (for the same message/same key). The IV provides the extra randomness to ensure that the same ciphertext is not generated across runs. Bug fixed #1643949.
target-dirwas no longer relative to current directory but to
datadirinstead. Bug fixed #1611568.
Backup would still succeed even if xtrabackup would fail to write the metadata. Bug fixed #1623210.
Some older versions of MySQL did not bother to initialize page type field for pages which are not index pages (see upstream #76262 for more information). Having this page type uninitialized could cause xtrabackup to crash on prepare. Bug fixed #1641426.
Percona XtraBackup would fail to backup MariaDB 10.2 with the
unsupported server versionerror message. Bug fixed #1602842.
Fixed misleading error message about missing metadata. Bug fixed #1557027.
Backing up with an SSL user didn’t work correctly. Bug fixed #1546872.