This script is Copyright (C) 2014 Tenable Network Security, Inc.
The remote openSUSE host is missing a security update.
Percona XtraBackup was updated to 2.1.6 [bnc#852224]
- New Features :
- New innobackupex --force-non-empty-directories option
- now supports logs created with the new log block
- New Features specific to MySQL 5.6: option
innodb_log_checksum_algorithm in Percona Server 5.6
- Bugs Fixed :
- innobackupex --copy-back fails on empty
- A fixed initialization vector (constant string) was used
while encrypting the data. This opened the encrypted
stream/data to plaintext attacks among others.
- innobackupex --version-check is now on by default.
- Since Version Check is enabled by default, new optin
--no-version-check option has been introduced to disable
- xtrabackup_slave_info didn't contain any GTID
information, which could cause master_auto_position not
to work properly
- now supports absolute paths in innodb_data_file_path
- 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
- wasn't able to perform backups to the NFS mount in some
NFS configurations, because it was trying to preserve
- unable to perform backup if innodb_log_arch_dir variable
was used in server configuration
- Race condition in start_query_killer child code could
cause parent MySQL connection to close.
- Bugs Fixed specific to MySQL 5.6 :
- 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.
- 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
- update and tag percona-xtrabackup-2.1.x-nodoc.patch
See also :
Update the affected xtrabackup packages.
Risk factor :
Low / CVSS Base Score : 2.1