Dear MySQL users,
MySQL Enterprise Backup 8.0.24, 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.24 supports only the MySQL Server 8.0.24.
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.
A brief summary of the changes in MySQL Enterprise Backup (MEB)
since the previous version is given below.
MySQL Enterprise Backup 8.0.24, 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.24 supports only the MySQL Server 8.0.24.
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.
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.24 (2021-04-20) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The --rename option now works with both full and partial restores: + If the --include-tables and --exclude-tables options are not used, all tables in the backup are restored, with the table selected by the --rename option renamed as specified. + If the --include-tables and --exclude-tables options are used, all tables selected by the two options together are restored, with the table selected by the --rename option renamed as specified. (Bug #31947026) Bugs Fixed * There were sporadic failures of backups involving encrypted InnoDB tables with the error "The encrypted table . . . is not initialized" when repeated DDL operations on the tables took place during the backup operations. (Bug #32495740) * When backing up tables that used MySQL Enterprise Transparent Data Encryption (TDE), if no password was provided using the --encrypt-passord option, mysqlbackup quit unexpectedly. With this fix, mysqlbackup throws a proper error and aborts the operation in the situation. (Bug #32486697) * Backups failed when backing up tables that used the keyring_hashicorp plugin for InnoDB table encryption. (Bug #32284801) * mysqlbackup quit unexpectedly at the end of a backup to a tape using the NetWorker software. (Bug #32081275) * The --include-tables and --exclude-tables options were ignored during a restore of a TTS backup taken with full locking (i.e., with --use-tts=with-full-locking). (Bug #31947026) * A restore of a compressed backup failed if the backed-up server did not use .ibd as the extension for InnoDB tablespaces. (Bug #31596356) * Backups for a server containing encrypted InnoDB tables failed when the server was of 64-bit and mysqlbackup was of 32-bit (or vice versa). It was due to the way keyring files were handled in the situation, which has been fixed by this patch. (Bug #29292085)