| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: xtrabackup | Distribution: SUSE Linux Enterprise 15 SP3 |
| Version: 2.4.10 | Vendor: openSUSE |
| Release: bp153.1.17 | Build date: Sat Mar 6 10:51:49 2021 |
| Group: Productivity/Archiving/Backup | Build host: obs-power8-04 |
| Size: 42829639 | Source RPM: xtrabackup-2.4.10-bp153.1.17.src.rpm |
| Packager: https://bugs.opensuse.org | |
| Url: http://www.percona.com/software/percona-xtrabackup/ | |
| Summary: Online backup for MySQL / InnoDB | |
Percona XtraBackup is an online (non-blocking) backup solution for InnoDB engines. It features uninterrupted transaction processing during backups for InnoDB, but can also backup MyISAM tables.
GPL-2.0-only
* Thu Apr 26 2018 guillaume.gardet@opensuse.org
- Remove unneeded patch:
* percona-xtrabackup-2.4.9-aarch_buildfix.patch
* Sun Apr 01 2018 astieger@suse.com
- Percona XtraBackup 2.4.10:
* Rebased to MySQL 5.7.19
* Fix xbcrypt failure with --encrypt-key-file option
* Fix lock-up on simultaneous usage of --lock-ddl and
- -lock-ddl-per-table
* Fix deadlock in prepare stage related to the maximum number
of pending reads
* Abort backup when encountering tablespaces with a corrupted
first page instead of skipping
- Use %license (boo#1082318)
* Wed Mar 14 2018 ro@suse.de
- compile some files with -O0 to allow build on aarch64
- add percona-xtrabackup-2.4.9-aarch_buildfix.patch
- add _constraints file: min 6G mem, min 8G diskspace
* Mon Dec 11 2017 astieger@suse.com
- Percona XtraBackup 2.4.9:
* xbcrypt now has an ability to decrypt files in parallel by
specifying the number of threads with the xtrabackup
- -encrypt-threads option
* xtrabackup --copy-back option can now be used with xtrabackup
- -parallel option to copy the user data files in parallel (redo
logs and system tablespaces are copied in the main thread)
* Various fixes to slave_info writing
* Various fixes for crashes under certain circumstances
* Wed Nov 22 2017 dmueller@suse.com
- set default unix socket address to the mariadb socket location
* Tue Aug 08 2017 astieger@suse.com
- Percona XtraBackup 2.4.8:
* Support MySQL 5.7, rebased to MySQL 5.7.13
* Support for InnoDB tablespace encryption
add --reencrypt-for-server-id option
* Support SHA256 passwords (via SSL connection)
* Support command options for secure connections
* xbcrypt format changes, backups are incompatible with 2.3.x
* Add --remove-original option to remove encrypted/compressed
files after operations
* Use hwardware accellerated crc32 implementaiton
* Add options to exclude tables (--tables-exclude) and databases
(--databases-exclude) from backup
* xbstream now supports parallel extraction (--parallel)
* xbstream now supports --decrypt, --encrypt-threads,
- -encrypt-key, --encrypt-key-file for decryption
* Add options for MDL locking (--lock-ddl, --lock-ddl-timeout,
- -lock-ddl-per-table)
- packaging changes:
* bundle boost 1.59.0
* dropped patches:
percona-xtrabackup-2.2.x-srv_buf_size.patch
percona-xtrabackup-2.3.8-gcc7-fallthrough.patch
percona-xtrabackup-2.3.8-gcc7-pointer-comparisons.patch
* Tue Aug 08 2017 astieger@suse.com
- Percona Xtrabackup 2.3.9:
* New --check-privileges option to check for system privileges
* Fix crash during prepare stage if index compaction was enabled
* Support building with OpenSSL 1.1
* xbstream could run out of file descriptors while extracting
backups which contains many tables
* Fix determining use of master_auto_postion on a slave to avoid
generating an invalid xtrabackup_slave_info file
* Fix crash backing up MariaDB 10.2.x with --ftwrl-* options
* Along with xtrabackup_checkpints file, xtrabackup now copies
xtrabackup_info file into directory specified by --extra-lsndir
* GTID position was not recorded when --binlog-info option was
set to AUTO
* bundled, patched libarchive updated to 3.3.1
* Wed Jul 19 2017 astieger@suse.com
- Remove unused bundled libarchive windows build files with
proprietary license keywords - bsc#1049458
* Fri Jun 02 2017 astieger@suse.com
- fix build with gcc7 bsc#1041250:
* percona-xtrabackup-2.3.8-gcc7-fallthrough.patch
* percona-xtrabackup-2.3.8-gcc7-pointer-comparisons.patch
* Wed May 10 2017 mrueckert@suse.de
- dont build shared libs for now.
* Wed May 10 2017 mrueckert@suse.de
- enable building with system ssl
* Wed May 10 2017 mrueckert@suse.de
- update to 2.3.8
- New Features
- Percona XtraBackup now uses hardware accelerated
implementation of crc32 where it is supported.
- Percona XtraBackup has implemented new options: xtrabackup
- -tables-exclude and xtrabackup --databases-exclude that work
similar to xtrabackup --tables and xtrabackup --databases
options, but exclude given names/paths from backup.
- The xbstream binary now supports parallel extraction with the
- -parallel option.
- The xbstream binary now supports following new options:
- -decrypt, --encrypt-threads, --encrypt-key, and
- -encrypt-key-file. When --decrypt option is specified
xbstream will automatically decrypt encrypted files when
extracting input stream. Either --encrypt-key or
- -encrypt-key-file options must be specified to provide
encryption key, but not both. Option --encrypt-threads
specifies the number of worker threads doing the encryption,
default is 1.
- Bugs fixed
- xtrabackup would not create fresh InnoDB redo logs when
preparing incremental backup. Bug fixed #1669592.
- xtrabackup --export can now export tables that have more than
31 index. Bug fixed #1089681.
- Unrecognized character \x01; marked by <-- HERE message could
be seen if backups were taken with the version check enabled.
Bug fixed #1651978.
- refreshed percona-xtrabackup-2.3.2-unbundle-jsnm.patch
* Thu Feb 23 2017 astieger@suse.com
- Percona XtraBackup 2.3.7
- New functionality:
* new --remove-original option for removing the encrypted and
compressed files once they’ve been decrypted/decompressed.
* now supports -H, -h, -u and -p shortcuts for --hostname,
- -datadir, --user and --password respectively.
- Bugs fixed:
* used username set for the server in a configuration file even
if a different user was defined in the user’s configuration file
* Incremental backups did not include xtrabackup_binlog_info and
xtrabackup_galera_info files
* --move-back option did not always restore out-of-datadir
tablespaces to their original directories
* innobackupex and xtrabackup scripts were showing the password
in the ps output when it was passed as a command line argument
bsc#1026729
* Incremental backup would fail with a path like ~/backup/inc_1
because xtrabackup didn’t properly expand tilde
* Sat Jan 14 2017 astieger@suse.com
- Percona XtraBackup 2.3.6, including one security fix:
* CVE-2016-6225: xbcrypt encryption IV not being set properly
(boo#1019858)
- New functionality:
* now supports SHA256 passwords
* new supports command options for secure connections
- Bugs fixed:
* intermittent assertion failures when not correctly identifying
server version
* Safe slave backup algorithm performed too short delays between
retries which could cause backups to fail on a busy servers
* fix compilation warnings with gcc6
* Backup would still succeed even if xtrabackup would fail to
write the metadata
* xbcloud now supports EMC ECS Swift API Authorization requests
* backup failed with MariaDB 10.2 with the unsupported server
version error message
* Sat Jul 16 2016 astieger@suse.com
- Percona XtraBackup 2.3.5, a bugfix release:
* Backup process would fail if --throttle option was used
* .ibd files for remote tablespaces were not copied back to the
original location pointed by the .isl files.
* Fix crash when called with insufficient parameters, like
specifying the empty --defaults-file option
* Change default value of --ftwrl-wait-query-type from "all" to
"update"
* Allow the datadir from my.cnf to override the one from
SHOW VARIABLES
* Fix failure on MariaDB if binary logs were in non-standard
directory
- Includes changes from 2.3.4:
* respect variables in backup-my.cnf without having to specify
- -defaults-file=backup-my.cnf
* abort the backup if innobackupex --rsync completed with error
* Fix logging ouf GTID info with MariaDB 10
* Fix silent skipping of extra arguments
* Allow connections to servers using legacy auth with new option
- -skip-secure-auth
* Tue Jul 05 2016 toddrme2178@gmail.com
- Fix Group tag.
* Sun Jan 17 2016 ecsos@opensuse.org
- 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
* Sat Dec 26 2015 astieger@suse.com
- xtrabackup does not strictly require mysqld, and this capability
is not longer provided by development MariaDB packages boo#959917
* Wed Oct 28 2015 astieger@suse.com
- Percona XtraBackup 2.3.2, a feature release:
* New utility xbcloud:
+ for up/downloading xbstream archives from/to cloud storage.
+ reads settings from [xbcloud] section in {/etc/,.}my.cnf
* Backwards compatibility:
+ The innobackupex script was rewritten in C and is a symlink
for xtrabackup. 2.2 command syntax is supported but
deprecated. Syntax for new features added to xtrabackup only.
+ Options: --lock-wait-query-type, --lock-wait-threshold and
- -lock-wait-timeout have been renamed to innobackupex
- -ftwrl-wait-query-type, --ftwrl-wait-threshold and
- -ftwrl-wait-timeout respectively.
* command line options changed to follow MySQL guidelines
* xtrabackup now also copies MyISAM tables and supports every
feature of innobackupex
* xtrabackup now supports --datadir
* Various bug fixes and improvements
- drop percona-xtrabackup-2.2.x-disable-default-version-check.patch
- add percona-xtrabackup-2.3.2-disable-version-check.patch to
remove feature completely
- unbundle the jsnm library,
adding percona-xtrabackup-2.3.2-unbundle-jsnm.patch
* Fri Oct 23 2015 astieger@suse.com
- Percona XtraBackup 2.2.13, a bugfix release:
* Improved the detection when the log block that has the different
number from what is expected
* Fixed false positive error: The log was not applied to the
intended LSN which was happening even when the redo log was
applied correctly
* xtrabackup_logfile was not compressed when --compress option was
used. Bug fixed #1242309.
* innobackupex wrote error message to STDOUT instead of STDIN
which broke xbstream and tar stream.
* Incremental backups did not work with MariaDB below 10.1.6.
* Wed Aug 12 2015 astieger@suse.com
- Percona XtraBackup 2.2.12, a bugfix release:
* fix segfault during the prepare phase of certain FTS pages.
* fix regression introduced in 2.2.8 which caused xtrabackup to
read a redo log from incorrect offset (assertion)
* fix pre-lock FLUSH TABLE written to binay log altering the GTID
* fix false successful completion on incomplete copy of redo log
* fix loosing correct table when when there are is more than one
tablespace with the same ID in the data directory
* fix missing revision_id in binaries.
* Fri May 29 2015 astieger@suse.com
- Percona XtraBackup 2.2.11:
* rebased on MySQL 5.6.24.
* fixed crash when preparing the backup taken on MySQL/Percona
Server 5.5 if there were open temporary tables during backup.
* fix failure to prepare the backup if the xtrabackup_logfile
was lager than 512GB
* Fix for bug #1403237 was incomplete, due to setting wrong
offset last copied batch of log records was copied from wrong
location.
* now executes an extra FLUSH TABLES before executing
FLUSH TABLES WITH READ LOCK to potentially lower the impact
from FLUSH TABLES WITH READ LOCK.
* fix regression from 2.2.10 which caused an error when taking
an incremental backup from MariaDB 10.
* now prints and stores the file based binlog coordinates in
xtrabackup_binlog_info even though GTID is enabled.
* no longer print warnings during the prepare phase about missing
tables with a filtering option (--databases, --tables, etc.)
* Thu Apr 02 2015 astieger@suse.com
- Percona XtraBackup 2.2.10:
* Decrypting backup with the wrong key would make the backup
unusable and unrecoverable.
* XtraDB Changed Page Tracking wasn't working with innobackupex.
* Fixed Percona XtraBackup assertion caused by dirty pages
remaining in the buffer pool after the log was fully applied.
* Backup will not be prepared and innobackupex will stop with an
error if the transaction log file is corrupted and it wasn't
applied to the intended LSN. Previously this was a warning.
* New status log-applied is introduced for backup prepared with
- -redo-only to avoid making the backup unusable by preparing
full or incremental backup without --redo-only and then
applying next incremental on top of it. Incremental backup now
can be applied only to backup in log-applied state, but not to
full-prepared as it was earlier.
* Wed Feb 25 2015 astieger@suse.com
- Downgrade qpress requirement from Requires to Recommends
* Wed Feb 25 2015 astieger@suse.com
- Percona XtraBackup 2.2.9:
* Percona XtraBackup was vulnerable to MITM attack which could
allow exfiltration of MySQL configuration information via
- -version-check option. [boo#919298] CVE-2015-1027 lp#1408375.
The openSUSE package has the version check disabled by default.
* xtrabackup_galera_info file isn't overwritten during the Galera
auto-recovery. lp#1418584.
* Percona XtraBackup now sets the maximum supported session value
for lock_wait_timeout variable to prevent unnecessary timeouts
when the global value is changed from the default. lp#1410339.
* New option --backup-locks, enabled by default, has been
implemented to control if backup locks will be used even if
they are supported by the server. To disable backup locks
innobackupex should be run with innobackupex --no-backup-locks
option. lp#1418820.
- Add percona-xtrabackup-2.2.9-nodoc.patch to make build work
without documentation directories deleted by spec file
* Thu Jan 22 2015 andreas.stieger@gmx.de
- Percona XtraBackup 2.2.8:
+ rebased on MySQL 5.6.22
+ Incremental backups would fail if the number of undo
tablespaces (innodb_undo_tablespaces) was more than 1. This was
caused by innobackupex removing the undo tablespaces during the
prepare phase.
+ Fixed multiple memory leaks detected by AddressSanitizer.
+ innobackupex could fail when preparing backup that was taken
from Percona Server 5.5 with log files (innodb_log_file_size)
bigger than 4G.
- Includes changes from 2.2.7:
+ Non-default value for innodb_log_block_size variable would
cause assertion when preparing the backup.
+ When Percona XtraBackup would run FLUSH ENGINE LOGS during the
backup process on GTID master, command was recorded to the
slave's binary log as well, which lead to inconsistency between
master and slave. Fixed by adding the NO_WRITE_TO_BINLOG clause
to FLUSH ENGINE LOGS to avoid interfering with binary log and
inconsistency with coordinates.
+ Exporting tables was inefficient when backup contained a large
(and unrelated) change buffer.
+ innobackupex was printing the GTID even if the GTID mode was
disabled which could cause confusion since it wasn't
incrementing. Now it prints only GTID when GITD mode is enabled
and when GTID mode is disabled it prints only filename and
position. innobackupex still prints GTID, filename and
positions if MariaDB server is being backed up.
* Mon Nov 03 2014 andreas.stieger@gmx.de
- Percona XtraBackup 2.2.6
- New Features:
+ now reads server options from SHOW VARIABLES rather than my.cnf
+ now has more verbose output during initial table scan
- Bugs Fixed:
+ innobackupex didn't take the default datadir, which caused
backups to fail if the datadir wasn't specified in my.cnf
+ innobackupex will now fail with an error when innobackupex
- -slave-info is used on a multi-threaded non-GTID slave,
because Exec_Master_Log_Pos cannot be trusted for a multi-
threaded slave.
+ InnoDB log scanning failure would cause backups to fail
+ --apply-log and --decompress marked mutually exclusive
+ now supports all option modifiers supported by upstream MySQL:
skip, disable, enable, maximum, loose
+ would fail to perform a full backup on Percona Server 5.5 if
innodb_log_file_size variable wasn't set in the [mysqld]
section of my.cnf
/usr/bin/innobackupex /usr/bin/xbcloud /usr/bin/xbcloud_osenv /usr/bin/xbcrypt /usr/bin/xbstream /usr/bin/xtrabackup /usr/share/licenses/xtrabackup /usr/share/licenses/xtrabackup/COPYING
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Apr 9 14:44:41 2024