- Percona XtraBackup 2.3.3, a bugfix release:
* Database directories were not removed if DROP DATABASE happened
during the backup.
* Backup would fail if Store backup history on the server feature
was enabled and backup was taken from server without binary
log enabled.
* Percona XtraBackup now fails with descriptive error message if
--defaults-extra-file is not specified first.
* Backup would fail if --rsync option was used without specifying
temporary folder.
* Fixed Percona XtraBackup crash which happened when it was used
for SST on MariaDB Galera Cluster caused by double free of
datadir‘ variable.
* --move-back did not respect the innodb_log_group_home_dir and
innodb_data_home_dir options which caused ib_logfiles and data
files not to be moved to correct location.
* xtrabackup_binlog_info was not updated correctly when applying
incremental backups.
* When using a --defaults-file option Percona XtraBackup would
complain about datadir being mismatched if it wasn’t explicitly
set in the defaults file.
* Fixed build issues by adding missing check in cmake script for
xxd presence.
* Percona XtraBackup would terminate backup process without error
if --slave-info option was used on a server not running as a
replication slave.
* innobackupex when used with --stream option would create an
empty directory with a timestamp as a name.
- update percona-xtrabackup-2.3.2-disable-version-check.patch
to percona-xtrabackup-2.3.3-disable-version-check.patch