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

MySQL Enterprise Backup 8.0.11 is the latest release for MySQL Enterprise Backup, and supports MySQL Server 8.0.11 only. For MySQL Server 5.7, please use MySQL Enterprise Backup 4.1; for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12.

• Deprecation and Removal Notes

• Functionality Added or Changed

• Bugs Fixed

Deprecation and Removal Notes

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

• The options --ssl and --ssl-verify-server-cert, already deprecated in MySQL Enterprise Backup 4.1, have now been removed. Use the --ssl-mode option instead to configure the security mode of your connection to the server. (WL #10221)

Functionality Added or Changed

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

• Servers' use of the keyring_encrypted_file and keyring_aws plugins is now supported. See Working with Encrypted InnoDB Tablespaces for details. (Bug #27127898, WL #10217)

• 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 relay log for a backed-up slave server, instead of being restored always to the data directory on the target slave server, is now restored by default to the same location it was found on the backed-up slave server. It can also be restored to a different location specified with the new --relay-log option. (Bug #25141738, Bug #83927, WL #8328)

• 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 location it was found on the backed-up server. It can also be restored to a different location specified with the new --log-bin option. (Bug #25141738, Bug #83927, WL #8328)

• The backup_history table now includes a server_uuid column, which stores the value of the server_uuid of the backed up server. (WL #11430)

• MySQL Enterprise Firewall is now supported. (WL #10268)

• A new option, --tls-version, specifies the protocols mysqlbackup permits for encrypted connections to MySQL servers. (WL #10218)

• 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. (WL #11070)

• mysqlbackup could not restore the auto increment values in tables and the corruptions flags for indexes onto a server. The tasks are now made possible by having mysqlbackup copying onto the target server blocks of redo logs that cover the duration from the latest checkpoint up to the backup end time, so that the restored server can, during the recovery phase at its first start, restore the auto increment values and the corruption flags using those blocks. (WL #10414)

• The buffer size for cloud transfers can now be specified using the new --cloud-buffer-size option. See Cloud Storage Options for details. (WL #11113)

• 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 for details. (WL #11112, WL #11113)

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 restored server failed to start. With this fix, mysqlbackup quits with a proper error (“Undo tablespace in the base backup not found”) in the situation.

  Users should make sure the undo log location does not change between successive restores of a full and an incremental backups, or of two incremental backups. (Bug #27530916)

• When restoring an incremental backup containing encrypted InnoDB tables to a MySQL Community Server, the password provided to mysqlbackup with the --encrypt-password option was never validated, so that when the wrong password was given, the restore still succeeded, but the restored server could not be started. With this fix, mysqlbackup throws an error and stops the restore if the password is wrong. (Bug #27483449)

• 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 of 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 #26495834, Bug #26373259, Bug #26093563, Bug #26423820, Bug #26497245, WL #10270)

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

• On macOS, mysqlbackup failed to determine the relay log file name correctly and thus could not back up the relay 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 case insensitive. (Bug #25548088)