Percona XtraBackup 2.1.6 发布了,XtraBackup 是一个用来备份 MySQL 的 InnoDB 数据库的开源工具。
改进记录如下:
New Features:
Percona XtraBackup now supports logs created with the new log block checksums option innodb_log_checksum_algorithm in Percona Server 5.6
New innobackupex --force-non-empty-directories option has been implemented. When specified, it makes innobackupex --copy-back option or innobackupex --move-back option transfer files to non-empty directories. No existing files will be overwritten. If --copy-back or --move-back has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.
A fixed initialization vector (constant string) was used while encrypting the data. This opened the encrypted stream/data to plaintext attacks among others. Bug fixed #1185343.
xtrabackup_slave_info file didn’t contain any GTID information, which could cause master_auto_position not to work properly. Bug fixed #1239670.
xtrabackup_56 was using CRC32 as the default checksum algorithm. This could cause error if the innodb_checksum_algorithm value was changed to strict_innodb value after a restore. Bug fixed #1247586.
xtrabackup_56 binary didn’t store the server’s innodb_checksum_algorithm value to backup-my.cnf. This value is needed because it affects the on-disk data format. Bug fixed #1248065.
Since Version Check is enabled by default in Percona XtraBackup 2.1.6, new innobackupex --no-version-check option has been introduced to disable it. Bug fixed #1248900.
Percona XtraBackup now supports absolute paths in innodb_data_file_path variable. Bug fixed #382742.
innobackupex wasn’t able to perform backups to the NFS mount in some NFS configurations, because it was trying to preserve file ownership. Bug fixed #943750.
Percona XtraBackup wouldn’t back up the empty directory created with mkdir (i.e. test) outside of the server which could lead to inconsistencies during the Percona XtraDB Cluster State Snapshot Transfer. Bug fixed #1217426.
If the innodb_log_arch_dir variable was specified in the Percona Server configuration file my.cnf, Percona XtraBackup was unable to perform the backup. Bug fixed #1227240.
Race condition in start_query_killer child code could cause parent MySQL connection to close. Bug fixed #1239728.
Percona XtraBackup 2.1.6 发布
Percona XtraBackup 2.1.6 发布了,XtraBackup 是一个用来备份 MySQL 的 InnoDB 数据库的开源工具。
改进记录如下:
New Features:
innobackupex --force-non-empty-directories
option has been implemented. When specified, it makesinnobackupex --copy-back
option orinnobackupex --move-back
option transfer files to non-empty directories. No existing files will be overwritten. If--copy-back
or--move-back
has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.Bugs Fixed:
innobackupex --copy-back
would fail ifinnodb_data_home_dir
is empty. Bug fixed #1049291.innobackupex --version-check
is now on by default. Bug fixed #1227988.xtrabackup_slave_info
file didn’t contain anyGTID
information, which could causemaster_auto_position
not to work properly. Bug fixed #1239670.CRC32
as the default checksum algorithm. This could cause error if the innodb_checksum_algorithm value was changed tostrict_innodb
value after a restore. Bug fixed #1247586.innodb_checksum_algorithm
value tobackup-my.cnf
. This value is needed because it affects the on-disk data format. Bug fixed #1248065.innobackupex --no-version-check
option has been introduced to disable it. Bug fixed #1248900.innodb_data_file_path
variable. Bug fixed #382742.NFS
mount in someNFS
configurations, because it was trying to preserve file ownership. Bug fixed #943750.mkdir
(i.e. test) outside of the server which could lead to inconsistencies during the Percona XtraDB Cluster State Snapshot Transfer. Bug fixed #1217426.my.cnf
, Percona XtraBackup was unable to perform the backup. Bug fixed #1227240.start_query_killer
child code could cause parent MySQL connection to close. Bug fixed #1239728.Other bugs fixed: #1248488, #1247057, #1250738, #1214274.