File xtrabackup.changes of Package xtrabackup
-------------------------------------------------------------------
Wed Dec 5 21:02:57 UTC 2012 - andreas.stieger@gmx.de
- update to 2.0.4
+ a regression introduced in XtraBackup 2.0.2 caused incremental
backups to fail because the init parameter values were not
normalized to the values used inside InnoDB
+ a regression introduced in traBackup 2.0.2 didn’t take the
separate doublewrite tablespace into an account
+ XtraBackup was handling the separate doublewrite buffer file
incorrectly. File path of the doublewrite buffer wasn’t added
to the backup-my.cnf and after the restore old doublewrite buffer
file was used instead of one made during the prepare stage
+ XtraBackup now accepts the --innodb=force option, previously it
would throw an error if the option was set
+ Option safe-slave-backup wasn’t working correctly
+ In case safe-slave-backup-timeout was reached when using the
safe-slave-backup option, SQL_THREAD was left in stopped state
causing the slave thread to lag behind. This was fixed by
checking the initial SQL_THREAD state and starting it before
terminating with a timeout error and starting the SQL_THREAD
only if it was running initially.
+ In case of streaming backups, innobackupex would resume the
Xtrabackup process and then wait for it to finish before running
UNLOCK TABLES. This caused database to be unnecessarily locked
with FLUSH TABLES WITH READ LOCK. Innobackupex now waits only
till log copying is finished to unlock the databases
+ XtraBackup would fail on --apply-log when filesystem didn’t
support Linux AIO
+ XtraBackup binary would ignore innodb_use_native_aio when it’s
specified either in my.cnf or as a command line option
+ XtraBackup would print a warning message during the prepare
stage about innodb_file_io_threads being deprecated, even if the
variable wasn’t set
+ XtraBackup Galera tests can now be run concurrently
-------------------------------------------------------------------
Tue Oct 2 18:03:21 UTC 2012 - andreas.stieger@gmx.de
- update to 2.0.3
- new features:
* innobackupex now supports new --move-back option that can be used
instead of --copy-back in case there isn’t enough free disk space
on the server to copy files. As this option removes backup files,
it must be used with caution.
- bug fixes:
* Symlink for innobackupex-1.5.1 binary has been broken in the
previous version of XtraBackup.
* XtraBackup 2.0.2 was not backwards compatible which caused
incremental backups created with previous versions to fail on
prepare.
* Fix a regression that may potentially lead to a 5x increase in
disk space occupied by incremental backups.
* Fix a regression which caused incorrect handling of compressed
tablespaces with the page size of 16K, that were created between
the last full or incremental and the next incremental backup.
- packaging changes:
* improve upgrade from generic packages
-------------------------------------------------------------------
Tue Aug 14 18:22:39 UTC 2012 - andreas.stieger@gmx.de
- update to 2.0.2
* Fixed false positive test suite failures with grep 2.10
* Incremental backup would fail if a tablespace was created
between full and incremental backups.
* Assertion error in creating a compressed tablespace at delta
apply time has been fixed.
* If the table was renamed after the full backup, but before the
incremental backup has been taken, incremental backups would
fail when being prepared.
* When the variable innodb_log_block_size was set to 4096, backups
would fail in the prepare stage.
* Additional incremental backup tests have been added for the
incremental backup data page copy.
- update percona-xtrabackup-2.0.2-nodoc.patch
-------------------------------------------------------------------
Sat Aug 4 08:55:08 UTC 2012 - andreas.stieger@gmx.de
- add xtrabackup-nodoc.sh to source package - removes documentation
from pristine upstream source packages when maintaining package.
Not used during build or in binary package.
-------------------------------------------------------------------
Fri Aug 3 07:31:50 UTC 2012 - andreas.stieger@gmx.de
- remove documentation from MySQL and xtrabackup tarballs due to license
-------------------------------------------------------------------
Sat Jul 7 13:46:00 UTC 2012 - andreas.stieger@gmx.de
- update to 2.0.1:
* After creating a full compressed backup, performing a
compressed/uncompressed incremental backup would fail because
xtrabackup_checkpoints was compressed. This has been fixed by
omitting xtrabackup_checkpoints from compression, so that a full
backup could be used for incremental backups without decompression.
* --copy-back was copying compressed *.qp files as well. This has been
fixed by skipping the compressed files while copying the data back.
* Streaming backups with --stream=tar would fail if the file size was
bigger than 8GB. Fixed by changing the libarchive format from USTAR
to restricted PAX which supports bigger file sizes.
* innobackupex was calling the tar utility unconditionally when
streaming ib_lru_dump and xtrabackup_galera_info. Which led to a
broken stream when the xbstream format was used.
* when --compress was used together with --stream=tar, xtrabackup was
silently creating a broken backup. Now it fails with an error
instead, suggesting to either use xbstream, or don't use compression
at all.
* --safe-slave-backup was resulting in incorrect binlog info, because
in some cases innobackupex confused the response from SHOW SLAVE
STATUS with the one from SHOW MASTER STATUS.
* xbstream would sometimes fail while extracting the backup.
* innodb_data_file_path was not written to backup-my.cnf, this was a
regression introduced in previous version.
* XtraBackup would fail to find the datadir when using mysqld_multi.
This was fixed by adding new option --defaults-group, to both
innobackupex and xtrabackup, now it can be specified which section
of my.cnf to handle.
* InnoDB tables with names containing: opt, par, CSV, MYD were backed
up twice. These tables were backed up by xtrabackup binary and by
innobackupex script. Regular expression for filtering database
directory contents was fixed.
* When run innobackupex with --apply-log, it was reading configuration
from the server configuration file instead of backup-my.cnf in
backup directory.
* innobackupex could copy files to a wrong directory when merging an
incremental backup to a full one.
* Incremental backups were not working correctly with --stream=tar.
This was fixed by making --incremental-lsn incompatible with
--stream=tar. XtraBackup will fail with an error message suggesting
to use --stream=xbstream.
* innobackupex failed to copy-back backup if destination dir wasn't
empty. Exceptions were added for my.cnf and master.inf` as
XtraBackup doesn't backup those files, so it won't overwrite
anything.
* innobackupex --copy-back could skip some files when copying from a
Windows filesystem mounted over NFS.
* XtraBackup binary was leaking file descriptors on --backup. This was
fixed by reusing the existing file descriptor so no leak occurs.
* There were no source files in tar.gz archive for Percona XtraBackup
2.0.0.
* XtraBackup|binary could fail with the log block checksum mismatch"
error when reading an partially written log block.
-------------------------------------------------------------------
Tue May 29 06:01:14 UTC 2012 - andreas.stieger@gmx.de
- cmake >= 2.6.3 is the actual minimum requirement, fixes 11.4
-------------------------------------------------------------------
Mon May 28 20:50:08 UTC 2012 - andreas.stieger@gmx.de
- remove HTML documentation in favour of online documentation
to fix factory build, also simplifies license.
- require cmake >= 2.8.5 to catch this requirement in OBS earlier
when building for SLE
-------------------------------------------------------------------
Wed Apr 25 18:44:01 UTC 2012 - andreas.stieger@gmx.de
- add mysql-5.1.59.tar.gz
- add mysql-5.5.17.tar.gz
- add .changes file
- build with RPM_OPT_FLAGS
- update project URL
- add HTML documentation built from source
- update to upstream 2.0.0:
* Percona XtraBackup can now save Galera replication information while
performing a backup when given the --galera-info option to innobackupex.
* XtraBackup now supports compressed backups. These backups can be done in a
parallel way, thus utilizing multiple CPU cores if needed. In previous
versions, compression was only possible with streaming backups + external
(usually single-threaded) compression utilities, which also had a number of
other limitations (e.g. could not be used with parallel file copying, it was
required to uncompress the entire backup to restore a single table).
* Percona XtraBackup now supports streaming incremental backups. In previous
versions streaming backups were performed by the innobackupex script but
incremental backups were done by the xtrabackup binary which calculated deltas
by scanning data files. Which meant those two feature were mutually exclusive,
i.e. one couldn’t do streaming incremental backups.
* As part of the backup, the LRU dump is now included as well.
* Support for compiling and running Percona XtraBackup against debug versions of
InnoDB. This is only for very advancedusers.
- For fixes included in previous releases, see
http://www.percona.com/doc/percona-xtrabackup/release-notes.html
-------------------------------------------------------------------
Tue Jun 9 00:00:00 UTC 2009 - lenz@grimmer.com
- Update to version 0.7
-------------------------------------------------------------------
Thu Apr 30 00:00:00 UTC 2009 - lenz@grimmer.com
- Update to version 0.6
-------------------------------------------------------------------
Thu Apr 9 00:00:00 UTC 2009 - lenz@grimmer.com
- Initial package added to the openSUSE Build Service (Version 0.5)
-------------------------------------------------------------------
Fri Mar 13 00:00:00 UTC 2009 - Vadim Tkachenko
- initial release
