Percona XtraBackup 2.1.1¶
This release is the first GA (Generally Available) stable release in the 2.1 series.
Percona XtraBackup now has support for compact_backups_ibk. This
feature can be used for taking the backups that will take less amount of disk
space. GA release now contains new
innobackupex --rebuild-threads that
can be used to specify the number of threads started by XtraBackup when
rebuilding secondary indexes on
--rebuild-indexes. This allows parallel processing of individual tables when
rebuilding the index.
Percona XtraBackup has implemented Encrypted Backups. This feature can be used to encrypt/decrypt both local and streamed backups in order to add another layer of protection to the backups.
innobackupex now uses Perl’s
DBD::MySQL package for server communication
instead of spawning the mysql command line client.
Support for InnoDB 5.0 and InnoDB 5.1 builtin has been removed from Percona XtraBackup.
After being deprecated in previous version, option
been completely removed in Percona XtraBackup 2.1.
innobackupex is using
SHOW MASTER STATUS to obtain binlog file and
position. This could trigger a bug if the server being backed up was standalone
server (neither master nor slave in replication) and binlog information wasn’t
available. Fixed by not creating
xtrabackup_binlog_info file when binlog
isn’t available. Bug fixed #1168513.
Percona XtraBackup would leave
xbtemp temp files behind due to a typo. Bug
Percona XtraBackup would assume the table has been dropped if the tablespace was renamed after it was scanned by Percona XtraBackup on startup and before Percona XtraBackup attempted to copy it. Bug fixed #1079700.
xtrabackup_pid file left inside tmpdir could cause SST
to fail. Fixed by fix checking if
xtrabackup_pid file exists once
innobackupex starts, and try to remove it or fail if it cannot be removed. Bug