MySQL Enterprise Backup 4.1.1 has been released

[Sreedhar S]

Dear MySQL users,

MySQL Enterprise Backup v4.1.1, 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 4.1.1 only supports MySQL 5.7.
For MySQL 5.6 and earlier, use MySQL Enterprise Backup 3.12.

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

Changes in MySQL Enterprise Backup 4.1.1    (2018-04-27)

Functionality Added or Changed

     * For MySQL Server 5.7.21 and later: Servers' use of the
       keyring_encrypted_file
       (http://dev.mysql.com/doc/refman/5.7/en/keyring-encrypted
       -file-plugin.html) and keyring_aws
       (http://dev.mysql.com/doc/refman/5.7/en/keyring-aws-plugin
       .html) plugins is now supported. See Working with
       Encrypted InnoDB Tables
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/
       meb-encrypted-innodb.html) 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 buffer size for cloud transfers can now be specified
       using the new --cloud-buffer-size option. See Cloud
       Storage Options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/
       backup-cloud-options.html) 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 these
       purposes. See Cloud Storage Options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/
        backup-cloud-options.html) for details.

Bugs Fixed

     * mysqlbackup failed to restore a TTS (transportable
       tablespace) backup if the row format of any TTS tables
       did not match the InnoDB default row format on the target
       server. This was because the row format of a table was
       not included in the backup if the table was created with
       the InnoDB default row format. With this fix, the row
       format is now always written to the backup, so that
       tables are always restored with the right row format.
       (Bug #27445546)

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

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

     * mysqlbackup did not indicate in its output whether an
       established connection with the server was encrypted or
       not. With this fix, the crucial information is now
       provided. (Bug #26919023)

     * On macOS, mysqlbackup failed to determine the relay log
       file name correctly if the relay log index file name was
       not specified. (Bug #25574605)

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

     * After restoring an incremental backup of a slave server,
       the file ibbackup_slave_info was missing from the meta
       folder under the backup directory on the target server.
       (Bug #25097753)

     * When a compressed backup was restored with the
       --innodb_data_home_dir option pointing to a restore
       location outside of the data directory, .ibd files were
       still being copied into the data directory, causing an
       exception to be thrown at the attempt to start the
       restored server. (Bug #24826986)
   
  On behalf MySQL RE team at Oracle
-Sreedhar S