MySQL Forums
Forum List  »  Announcements

MySQL Enterprise Backup 8.0.20 has been released
Posted by: Bjørn Munch
Date: April 27, 2020 12:58PM

Dear MySQL users,

MySQL Enterprise Backup 8.0.20, 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.20 supports only the MySQL Server 8.0.20.
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,
please use MySQL Enterprise Backup 3.12.

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


Changes in MySQL Enterprise Backup 8.0.20 (2020-04-27, General

Functionality Added or Changed

     * The tablespace_tracker
       file has been simplified: it now contains only two
       fields for each external tablespace: server_file_path and
       space_id. mysqlbackup no longer relies on the file for
       information on the backup_file_path and the tablespace
       type, which means that users no longer need to update the
       file when they move a directory backup to a new location.

     * Table-Level Recovery (TLR) is a new feature of MySQL
       Enterprise Backup that allows selective restores of
       tables or schemas from full backups; see Table-Level
       Recovery (TLR)
       for details.

     * The legacy option --include is now deprecated. A
       deprecation warning is now issued by mysqlbackup whenever
       the option is used. The --include-tables and
       --exclude-tables options should be used instead for
       partial backups and restores.

Bugs Fixed

     * A backup failed with ERROR: Bad table space file header
       when the server had more than one system tablespace
       files. It was because mysqlbackup looked for the
       tablespace file header at the wrong place, and this patch
       corrects the problem. (Bug #30983009)

     * During an incremental backup, mysqlbackup simply repeated
       the Server Repository Options when trying to print the
       Backup Configuration Options in its output. (Bug

     * Backups failed when the server used a keyring plugin and
       its sql_mode was set to ANSI_QUOTES. It was because
       mysqlbackup used the wrong kind of quotes in the
       situation when querying the server, and that has been
       fixed by this patch. (Bug #30920140)

     * An incremental optimistic image backup failed when the
       server was started with a non-default
       innodb_data_file_path value containing more than one
       InnoDB system tablespace file. It was because mysqlbackup
       could not handle the situation in which the two different
       files had the same space ID, and this patch fixes the
       problem. (Bug #30914039)

     * A partial restore of a TTS backup failed when the file
       path specified with the --datadir option contained extra
       slashes (/) when compared with the data directory file
       path the server was started with. With this fix, such
       extra slashes for the --datadir option are ignored. (Bug

     * During a backup operation, if any tablespace's encryption
       status was changed (for example, from encrypted to
       unencrypted or vice versa, and even if the table was
       eventually changed back to its original encryption
       status), mysqlbackup reported success, but it quit
       unexpectedly during the restore operation of the backup
       because of its inconsistency. With this fix, the
       encryption statuses of tablespaces are properly tracked
       throughout the backup operation, so that the tables are
       consistently backed up. (Bug #30599476)

     * When the --src-entry option was used with the extract
       command, a trailing slash in its value (for example, in
       foo/) was ignored, so that instead of extracting from the
       backup only those directories whose names ended with the
       value (for example, datadir/foo/), mysqlbackup also
       extracted all files whose paths contained the value (for
       example, datadir/bar/foo.sdi). With this fix, the
       trailing slash is honored, and it only causes folders
       whose names end with the value to be extracted.
       It is also clarified in the documentation that the value
       of the --src-entry option is actually used to match any
       files or non-empty folders that contain the value in
       their names, and a trailing slash is interpreted as
       described in the last paragraph. (Bug #30461403)

     * When there was a user-created mysql.backup_progress table
       on a server that was being backed up, mysqlbackup
       finished the backup successfully, but also printed error
       messages and recorded a backup failure in the
       backup_history table. With this fix, the backup is
       finished as normal with a warning. (Bug #30351172)

     * The binary log basename appeared as an empty string in
       the progress report of a copy-back-and-apply-log
       operation. (Bug #29936558)

     * When a data tablespace had the same name as an undo
       tablespace on the server, a compressed backup containing
       the tablespace could be created by mysqlbackup, but the
       backup could not be restored due to the filename
       conflict. With this fix, the backup fails in the
       situation. (Bug #29881640)

     * A backup failed when it involved encrypted InnoDB tables
       and the --skip-unused-pages option was used. (Bug

     * When a compressed backup was created with the
       backup-and-apply-log command and then restored using the
       copy-back-and-apply-log command, the redo log were
       missing from the restored server, causing an InnoDB error
       when the server was started. (Bug #29851603)

     * A backup failed when the --skip-unused-pages and
       --optimistic-busy-tables options were used together. (Bug

     * When the server to be backed up has super_read_only=ON,
       mysqlbackup gave the warning that the backup operation
       could not be logged even if the --no-history-logging
       option has already been used with the backup command.
       This patch removes the unnecessary warning. (Bug

     * A backup-and-apply-log operation failed for a TTS backup
       if the --compress option was used. (Bug #29639871)

     * An extract operation for the file
       meta/backup_variables.txt failed with mysqlbackup
       complaining that the value of the option --src-entry did
       not match any table in the backup. With this fix,
       mysqlbackup no longer throws an eorrr in the situation,
       but prints the message "The src-entry
       'backup_variables.txt' is by default extracted to
       backup-dir". (Bug #29519710)

     * During a backup operation, mysqlbackup printed messages
       regarding the encryption keyring even though the server
       did not utilize InnoDB table encryption. With this patch,
       mysqlbackup stops printing such messages in the
       situation. (Bug #29151380)

Options: ReplyQuote

Written By
MySQL Enterprise Backup 8.0.20 has been released
April 27, 2020 12:58PM

Sorry, you do not have permission to post/reply in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.