MySQL Enterprise Backup 8.0 Release Notes
MySQL Enterprise Backup 8.0.14 is the latest release for MySQL Enterprise Backup. It only supports MySQL Server 8.0.14. 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.
mysqlbackup now supports encrypted binary and relay log. See descriptions for the undo log files for details.
mysqlbackup now supports the
--ssl-fips-mode
option, which controls whether mysqlbackup
operates in FIPS mode. See FIPS Support for
details.
When working with a Group Replication cluster,
mysqlbackup quit unexpectedly near the end of
a backup operation when, in order to write to the
backup_history
table, it tried to connect
with an unencrypted connection to one of the nodes on which the
backup user had not logged on before. It was because, as a user
created with the
caching_sha2_password
plugin (enabled by default on MySQL 8.0 servers), the backup
user must log on with an encrypted connection when it connects
to the server for the first time; the attempt to log on thus
failed, and mysqlbackup could not handle the
failure. With this fix, at such failures,
mysqlbackup quits gracefully with the warning
that the backup operation is finished without updates to the
backup history.
(Bug #28893180)
An apply-incremental-backup
operation failed with an error (RDR1 ERROR: Unable to
remove relaylog files from full backup
) when the
incremental backup was created with the
--compress
option.
(Bug #28366241)
mysqlbackup quit unexpectedly during an
apply-incremental-backup
operation
if the backed up server had been started using relative paths
for --datadir
and
--log-bin
.
(Bug #28334521)
Attempts to restore a backup of a MySQL 5.7 Server to a MySQL
8.0 Server resulted in a strange error message
(Server_version is not obtained
). With this
fix, mysqlbackup now indicates that the
operation is not supported. For related information, see
Restoring a Backup with a Database Upgrade or Downgrade.
(Bug #27952379)
After restoring an incremental folder backup and putting its binary log at a specified location different from that for the base backup, the older binary log files of the base backup were not removed by mysqlbackup. (Bug #27890472)
mysqlbackup
quit unexpectedly when backing up
a MySQL Server of release 8.0.12 or later for the first time if
the ALTER
privilege on the
mysql.backup_history_new
table had not been
granted to the MySQL user with which
mysqlbackup
connected to the server. With
this fix, mysqlbackup
quits gracefully in the
situation after throwing the proper error.
Also, the CREATE
,
INSERT
, and
DROP
privileges on
mysql.backup_history_old
and
CREATE
,
INSERT
,
DROP
, and
ALTER
privileges on
mysql.backup_history_new
are now required
only for backing up for the first time a MySQL Server that has
been upgraded from 8.0.11 or earlier and has been backed up by
MySQL Enterprise Backup before.
(Bug #27879530, Bug #28546256)
Partial backups sometimes failed because full-text index files
had their file names matched by the regular expression provided
by the --include-tables
option, and
the files were then handled as ordinary tablespace files by
mysqlbackup. With this fix,
mysqlbackup excludes any full-text index
files from backups.
(Bug #25044900)