Dear MySQL users,
MySQL Enterprise Backup 8.0.13, 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 8.0.13 only supports MySQL Server 8.0.13. For
earlier versions of MySQL 8.0, use the MySQL Enterprise Backup version
with the same version number as the server.  For MySQL server 5.7,
please use MySQL Enterprise Backup 4.1 and for MySQL Server 5.6 and
5.5, please use MySQL Enterprise Backup 3.12.
A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 8.0.13 is given below.


Changes in MySQL Enterprise Backup 8.0.13 (2018-10-22)

     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed

     * mysqlbackup now supports backup compression (the use of
       the --compress and --uncompress options) for incremental
       backups (except for incremental backups created with the
       --incremental-with-redo-log-only option).

     * mysqlbackup now supports transparent page compression for
       InnoDB tables. The support is enabled by setting the
       mysqlbackup option --compress-method=punch-hole; see
       description for the option for details.

Bugs Fixed

     * mysqlbackup hung when a backup operation failed due to a
       full disk. With this fix, mysqlbackup quits gracefully in
       the situation by throwing an error. (Bug #28399821)

     * A mysqlbackup operation on an image stored on an
       OpenStack cloud storage service sometimes failed with a
       segmentation fault or a bad URL error. It was because of
       a race condition caused by an uninitiated variable, which
       has been eliminated by this fix. (Bug #28189239, Bug

     * Backups for databases with encrypted InnoDB tables failed
       when the --compress option was used. (Bug #28177466)

     * A mysqlbackup operation on an image stored on an
       OpenStack cloud storage service failed with a 401
       Unauthorized error when the operation took a long time
       and the authentication token for the cloud access
       expired. With this fix, a separate thread in mysqlbackup
       requests a new token from the OpenStack cloud service in
       that situation, so that the operation can continue. (Bug

     * When an incremental backup was restored without using the
       --log-bin option, the binary log was not restored to its
       original location on the backed up server, but to the
       location specified by --log-bin earlier during the
       restore of the base backup. The same occurred for relay
       logs of incremental backups for slaves when the
       --relay-log option was not used. (Bug #27545745)

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to