MySQL Enterprise Backup 8.0.28 is the latest release for MySQL Enterprise Backup. It only supports MySQL Server 8.0.28. 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.
The TLSv1 and TLSv1.1 connection protocols were deprecated in MySQL 8.0.26 and are now removed in MySQL 8.0.28. The removed protocols are considered invalid for use with the
--tls-versionoption for connecting mysqlbackup to the server. Instead, connections can be made using the more-secure TLSv1.2 and TLSv1.3 protocols. (Bug #33513289)
--forceoption has been deprecated: it is now ignored by mysqlbackup, and a warning appears whenever it is used with a mysqlbackup command.
Old page tracking files on the server created by the mysqlbackup component can now be purged by a new loadable function,
mysqlbackup_page_track_purge_up_to(). See Incremental Backup Using Page Tracking for details. Thanks to Rahul Malik for contributing to this feature. (Bug #33529452, Bug #105406)
Two manifest files have been added to the distribution packages for MySQL Enterprise Backup:
INFO_BINcontains information about the build environment used to produce the distribution, and
INFO_SRCprovides information about the product version and the source repository from which the distribution was produced. (Bug #33510726)
A cloud backup to GCP object storage failed when trunk transfer was enabled and the backup had more than 32 parts. (Bug #33460078)
Backing up to tapes sometimes failed when the
--sbt-environmentoption was used. It was because the variables specified with the option were passed to the media management software only after the backup process had already been initialized. This patch makes mysqlbackup pass the variables before the process initialization. (Bug #33454630)
During a backup, when something went wrong and the redo log's end LSN was lower than the LSN checkpoint on the server, the operation ended with a
No space left on deviceerror. This was because the truncation length for the
ibbackup_logfilebecame negative in that case. With this fix, mysqlbackup reports the problem as a file corruption error when the backup fails in the situation. (Bug #33272539)