Percona XtraBackup 2.3.3 for MySQL Percona is glad to announce the release of Percona XtraBackup 2.3.3 on December 17th, 2015. Downloads are available from our download site or Percona Software Repositories.

Percona XtraBackup enables MySQL backups without blocking user queries, making it ideal for companies with large data sets and mission-critical applications that cannot tolerate long periods of downtime. Offered free as an open source solution, Percona XtraBackup drives down backup costs while providing unique features for MySQL backups.

This release is the current GA (Generally Available) stable release in the 2.3 series.

Bugs Fixed:

  • Database directories were not removed if DROP DATABASE happened during the backup. Bug fixed #1461735.
  • Backup would fail if Store backup history on the server feature was enabled and backup was taken from server without binary log enabled. Bug fixed #1509812.
  • Percona XtraBackup now fails with descriptive error message if --defaults-extra-file option is not specified first. Bug fixed #1511451.
  • Backup would fail if --rsync option was used without specifying temporary folder. Bug fixed #1511701.
  • Fixed Percona XtraBackup crash which happened when it was used for SST on MariaDB Galera Cluster caused by double free of datadir variable. Bug fixed #1512281.
  • --move-back option 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 back to correct location. Bug fixed #1512616.
  • xtrabackup_binlog_info was not updated correctly when applying incremental backups. Bug fixed #1523687.
  • When using a --defaults-file option Percona XtraBackup would complain about datadir being mismatched if it wasn’t explicitly set in the defaults file. Bug fixed #1508448.
  • Fixed build issues by adding missing check in cmake script for xxd presence. Bug fixed #1511267.
  • Percona XtraBackup would terminate backup process without error if --slave-info option was used on a server not running as a replication slave. Bug fixed #1513520.
  • innobackupex when used with --stream option would create an empty directory with a timestamp as a name. Bug fixed #1520569.

Other bugs fixed #1523728 and #1507238.

Release notes with all the bugfixes for Percona XtraBackup 2.3.3 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

6 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Parker

great job!

xl.wei

Does Percona XtraBackup 2.3 including 2.3.2 and 2.3.3 support MySQL 5.7.9?

In my test, it fail.

[root ~]#
[root ~]# mysql -uroot -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 19
Server version: 5.7.9-log Source distribution

Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> select @@version;
+———–+
| @@version |
+———–+
| 5.7.9-log |
+———–+
1 row in set (0.00 sec)

mysql> exit
Bye
[root ~]#
[root ~]# xtrabackup –version
xtrabackup version 2.3.3 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 525ca7d)
[root ~]#
[root ~]# xtrabackup –defaults-file=/usr/local/mysql/my.cnf –user=root –password=123456 –datadir=/data/3306 –backup –target-dir=/data/testbak
151218 00:37:11 version_check Connecting to MySQL server with DSN ‘dbi:mysql:;mysql_read_default_group=xtrabackup’ as ‘root’ (using password: YES).
Failed to connect to MySQL server as DBD::mysql module is not installed at – line 1327.
151218 00:37:11 Connecting to MySQL server host: localhost, user: root, password: set, port: 0, socket: (null)
Error: Unsupported server version: ‘5.7.9-log’. Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
[root ~]#

So, What happened?

Hank Yoon

thanks, solved my backup

Felisa

Is there a projected release date of Percona XtraBackup support for MySQL 5.7??