MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Balasubramanian Kandasamy Date:April 19 2018 1:01pm
Subject:MySQL Enterprise Backup 8.0.11 has been released
View as plain text  
Dear MySQL users,

MySQL Enterprise Backup 8.0.11, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) 
as our latest GA release. This release will be available on eDelivery 
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 8.0.11 is given below.

Changes in MySQL Enterprise Backup 8.0.11 (2018-04-19, General

    MySQL Enterprise Backup 8.0.11 is the latest release for
    MySQL Enterprise Backup. It only supports MySQL Server
    8.0.11. 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.

      * Functionality Added or Changed

      * Bugs Fixed

Functionality Added or Changed

      * Offline backups are no longer supported by mysqlbackup.
        As a result, a number of options used for offline
        operations have been removed. See What's New in
        Enterprise Backup 8.0?
        for details. (Bug #27429244)

      * The server option --secure-auth, deprecated since MySQL
        5.7.5, is no longer supported by mysqlbackup. (Bug

      * Servers' use of the keyring_encrypted_file
        and keyring_aws
        plugins is now supported. See Working with
        Encrypted InnoDB Tables

        for details. (Bug #27127898)

      * Information on the executed GTIDs is now included in the
        mysqlbackup output and the backup log when the
backed up
        server has GTIDs enabled. (Bug #25978803)

      * The backup_history table now includes a server_uuid
        column, which stores the value of the server_uuid of
        backed up server.

      * The options --ssl and --ssl-verify-server-cert, already
        deprecated in MySQL Enterprise Backup 4.1, have now
        removed. Use the --ssl-mode option instead to
        the security mode of your connection to the server.

      * MySQL Enterprise Firewall
        is now supported.

      * A new option, --tls-version, specifies the protocols
        mysqlbackup permits for encrypted connections to

      * A file now tracks information of external tablespaces
        for a backup or restore in JSON format. See
        description for tablespace_tracker

        in Types of Files in a Backup

        for details.

      * The relay log for a backed-up slave server, instead of
        being restored always to the data directory on the
        slave server, is now restored by default to the same
        location it was found on the backed-up slave server.
        can also be restored to a different location
        with the new --relay-log option.

      * The binary log for a backed-up server, instead of being
        restored always to the data directory on the target
        server, is now restored by default to the same
        it was found on the backed-up server. It can also be
        restored to a different location specified with the
        --log-bin option.

      * The buffer size for cloud transfers can now be specified
        using the new --cloud-buffer-size option. See Cloud
        Storage Options

        for details.

      * HTTP Basic Authentication and non-chunked transfer are
        now supported for backup and restore using OpenStack
        Swift-compatible object storage services. Two new
        options, --cloud-basicauth-url and
        --cloud-chunked-transfer, have been introduced for
        purposes. See Cloud Storage Options

        for details.

Bugs Fixed

      * After restoring a full backup, if the following restore
        of an incremental backup changed the restore
location of
        the undo log, either mysqlbackup hung, or the
        server failed to start. With this fix, mysqlbackup
        with a proper error ("Undo tablespace in the base
        not found") in the situation.
        Users should make sure the undo log location does
        change between successive restores of a full and an
        incremental backups, or of two incremental backups.

      * mysqlbackup failed to backup to an Amazon S3 cloud
        storage. (Bug #27231229)

      * An apply-incremental-backup operation corrupted the
        non-InnoDB files in its target backup when the sizes
        those files are smaller in the incremental backup
than in
        the target backup. (Bug #27001934)

      * mysqlbackup could not establish a connection to the
        server with a Unix socket using the option
        --protocol=SOCKET. (Bug #26977679)

      * A number of memory leaks were observed when running
        mysqlbackup. They have now been fixed. (Bug
        Bug #26373259, Bug #26093563, Bug #26423820, Bug

      * After applying an incremental backup created with the
        --incremental-with-redo-log-only option to a full
        the full backup's binary log became corrupted. (Bug

      * On macOS, mysqlbackup failed to determine the relay log
        file name correctly and thus could not back up the
        log for a slave server. (Bug #25574605)

      * mysqlbackup only accepts values for --ssl-mode in upper
        case. With this fix, the option's value has become
        insensitive. (Bug #25548088)

      * In a Group Replication
        setting for MySQL servers, when changes were made
        to one group member and a backup was taken on
        the relay log for the replication applier was
        from the backup, so that the restored server could
not be
        started. (Bug #25534078)

      * mysqlbackup could not restore the auto increment values
        in tables and the corruptions flags for indexes onto
        server. The tasks are now made possible by having
        mysqlbackup copying onto the restored sever blocks
        redo logs that cover the during from the latest
        checkpoint to the time of backup, so that the server
        after restart, restore the incremental values and
        corruption flags using those blocks.

On Behalf of Oracle/MySQL Release Engineering Team
Balasubramanian Kandasamy

MySQL Enterprise Backup 8.0.11 has been releasedBalasubramanian Kandasamy19 Apr