Dear MySQL users,
MySQL Enterprise Backup v4.0.2, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.
MySQL Enterprise Backup v4.0.2 supports only the MySQL Server 5.7.9 and above.
For any earlier versions of the MySQL server, please use
MySQL Enterprise Backup 3.12 instead.
A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.0.2 is given below.
Changes in MySQL Enterprise Backup 4.0.2 (2016-07-26)
Functionality Added or Changed
* When there were no tables matching the regular expression
specified with the --include-table option during a backup
operation, mysqlbackup still created a backup, which
contained an empty folder for each database on the
server. mysqlbackup now throws an error when
--include-tables selects no tables to be backed up. (Bug
#18114353)
* MySQL Enterprise Backup can now backup and restore
encrypted InnoDB tables. See Working with Encrypted
InnoDB Tables and Options for Working with Encrypted
InnoDB Tablespaces for details.
Bugs Fixed
* When trying to restore a compressed image backup of a
server that had separate undo tablespaces residing in the
data directory with the copy-back-and-apply-log command,
the operation failed at the apply-log phase, as
mysqlbackup could not load the undo tablepaces. (Bug
#23583961)
* Attempts to restore an image backup from the cloud using
the --skip-binlog option failed with a "global tail magic
mismatch" error. This was because mysqlbackup failed to
perform a non-sequential read from the cloud with gaps
caused by the skipping of the binary logs. This fix makes
sure mysqlbackup can perform such reads. (Bug #23534700)
* When a compressed backup was being restored, if the undo
logs had been put into separate tablespaces outside of
the data directory on the backed up server, they got
restored twice, once mistakenly as general tablespaces
with the .ibd extension, and once as undo tablespaces
without a file extension. This fix makes sure they are
restored normally as undo tablespaces only. (Bug
#23179194)
* An extract operation for an image backup failed with a
checksum mismatch error in cases when, during the backup,
an InnoDB tablespace file kept growing in size, and
mysqlbackup failed to put the correct file size in its
file header. (Bug #22905984)
References: This issue is a regression of: Bug #22613568.
* During a mysqlbackup operation on a compressed backup
(that is, the --uncompress option was used), mysqlbackup,
in some situations, wrote to the log file multiple
instances of the message "ERROR: InnoDB: file write at
offset > 4 GB," even though the operation was actually
successful. (Bug #22733760)
* Occasionally, some files were missing from an image
backup created by the --backup-to-image command. It was
due to an internal race condition, which this fix
eliminates. (Bug #19600687)
The complete manual for MEB 4.0.2 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html
The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).
You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.
Your feedback is greatly appreciated!
Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"
Thanks,
On behalf MySQL RE team at Oracle
Sreedhar S