X

MySQL and MySQL Community information

  • March 17, 2015

MySQL Enterprise Backup 3.12.0 has been released

Guest Author

MySQL Enterprise Backup team is excited to announce the new release of MySQL Enterprise Backup (MEB) 3.12.0.

 MEB 3.12.0 focuses on enhancing the capabilities of the product that would be very useful to the database administrators.

New functionality added

Support for Open Stack Object Storage

In the last release of MEB, we added cloud support of Amazon S3 to do backups and restore from MEB. Now in MySQL Enterprise Backup 3.12.0, we have added cloud backup and restore using OpenStack Object Storage ("Swift") 1.0.
Authentication can be handled either through Swift's own TempAuth authentication system or the OpenStack Identity Service (Keystone) 2.0.

 A number of new command options have been introduced to support the OpenStack Object Storage. Details of Cloud Storage Options are available here


Table rename while selective restore

MySQL Enterprise Backup now supports renaming of a table while restoring a table to an online server.

This feature will be very useful for DBAs while restoring any table from a backup to recover specific data while keeping the original one intact.

Bugs Fixed

In MEB 3.12.0 we have addressed quite a number of bug fixes. I have listed a few of them below. For more information please refer documentation.

Binary Logs:
•The binary log file and relay log files (in the case of slave server) are now compressed when they are being included in a compressed backup and decompressed during a restore. (Bug #19149210)


•If a binary log file on the server got removed when backup was taking place, the backup failed, as mysqlbackup could not find the binary log file it wanted to copy into the backup. With the fix, mysqlbackup continues to finish the backup operation even if some binary log files have been deleted. Also, only the binary log files listed in the binary log index file are copied back to a server during a restore, so that purged binary log files, even backed up, are not restored. (Bug #19849326)

Backup:
•When mysqlbackup encountered a corrupted .frm file during a backup, it threw an error, tried to continue with the backup, and then hung eventually. With this fix, mysqlbackup just gives a warning message ("WARNING: An error occurred while adding manifest information for backup"), and then continues with the backup as usual. (Bug #19608231)


•The list-image operation on cloud backups failed. This was because the operation requires transfer of data without buffering, but mysqlbackup was transferring data in buffered mode by default. This fix makes mysqlbackup download data for the operation without buffering which is possible as long as the cloud proxy supports HTTP range hearers. (Bug #19162974)


•After a RESET SLAVE statement was executed on a slave server, a subsequent backup for the slave server failed with an error, as mysqlbackup could not copy the relay log file from the server. This was because mysqlbackup could not detect the location of the current relay log after the slave reset, and this fix makes sure mysqlbackup knows how to do that. (Bug #20180440, Bug #75074)

Restore:
•The –force option can now be used during the restore of a full backup to overwrite existing data in a non-empty target directory. (Bug #19266491)


•When trying to restore a non-TTS backup to a running server, mysqlbackup overwrote the data on the server without giving any warning. This fix makes mysqlbackup terminate the restore of a non-TTS full backup with an error whenever it finds the target data directory to be non-empty, and then issue a message that the –force option should be used if the user wants the original data to be overwritten. (Bug #19266491)


•When restoring an incremental backup using the copy-back-and-apply-log subcommand on Windows platforms, the operation failed when long file paths were used in the command-line options. This has been fixed in this release.(Bug #18448617)


•If an incremental image backup contained a large number of pages from a single table, the restore of the incremental backup using the copy-back-and-apply-log command might fail. This issue is fixed in MEB 3.12.0.(Bug #20492274)


MEB 3.12.0 is supported on the following platforms:

- Windows

- Debian 6.0, RHEL 6, RHEL 7, Oracle Linux, Suse 11,Ubuntu 12.04

- Solaris 10 Sparc/x86, Solaris 11 Sparc/x86

- Freebsd8

- MacOS 10.6

MEB 3.12.0 is now available in My Oracle Support and will soon be available in Oracle Cloud Delivery .


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.