Percona is glad to announce the release of Percona XtraBackup 2.1.0-rc1 on May 7, 2013. Downloads are available from our download site here. For this RC release, we will not be making APT and YUM repositories available, just base deb and RPM packages
This is an Release Candidate quality release and is not intended for production. If you want a high-quality, generally available release, the current stable version should be used (currently 2.0.7 in the 2.0 series at the time of writing).
- This version of Percona XtraBackup has implemented full support for new MySQL 5.6 features (
GTID, remote/transportable tablespaces, separate undo tablespace, 5.6-style buffer pool dump files).
- Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6 buffer pool dumps can be produced and loaded for faster server warmup after the start. This feature is similar to the Dump/Restore of the Buffer Pool in Percona Server. MySQL 5.6 buffer pool dump is copied into backup directory during the backup stage. During the copy back stage (restore) it is copied back to data directory. After the backup is restored buffer pool dump can be loaded by the server either automatically on startup or on demand.
- Time interval between checks done by log copying thread is now configurable by innobackupex –log-copy-interval. Making the interval configurable allows to reduce the time between checks which can prevent XtraBackup failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
- Percona XtraBackup now stores the
GTIDvalue in the
xtrabackup_binlog_infowhen doing the backup of MySQL and Percona Server 5.6 with the
GTIDmode enabled. Example of how this information can be used to create/restore a slave can be found in this blogpost.
- Percona XtraBackup option xtrabackup –export now supports transportable tablespaces introduced in MySQL 5.6. This option can be used to produce 5.6-style metadata files, that can be imported by
ALTER TABLE IMPORT TABLESPACEon MySQL and Percona Server 5.6 as described in Exporting and Importing Tables guide.
- Percona XtraBackup would crash when preparing the 5.6 backup with partitioned tables. Bug fixed #1169169.
- Tables that were dropped between taking a full backup and an incremental one were present in the full backup directory, and were not removed when incremental backups has been merged. Fixed by removing files corresponding to tables that are missing in the incremental backup directory. Bug fixed #856400.
- Percona XtraBackup would leave stale
xtrabackup_tmp*files in the datadir after applying incremental backups. Bug fixed #1079135.
- If there are thousands of tables and slow IO then XtraBackup can spend a lot of time opening all the tablespaces. Optimization has been implemented and XtraBackup now avoids loading non-relevant tablespaces when partial backup is being taken which speeds up the backup process. Bug fixed #1130145.
- Due to different implementation in MySQL 5.6 error messages were not printed to
stderrdirectly. Because of that all InnoDB error or diagnostic messages are never printed by
xtrabackup_56. Bug fixed #1169971.
- innobackupex would still run with
FLUSH TABLES WITH READ LOCKeven if xtrabackup would fail when copying logs. Fixed by terminating xtrabackup process immediately on log copying failure. Bug fixed #1170806.
- Percona XtraBackup would leave
xbtemptemp files behind due to a typo. Bug fixed #1172016.
- innobackupex wasn’t handling the innodb_data_file_path option which could cause backup to fail. Bug fixed #1169726.
- For the Debian and the Linux binaries, the –version message which should include the revision was showing “undefined”. Bug fixed #1171721.