Related Documentation Download these Release Notes
PDF (US Ltr) - 269.2Kb
PDF (A4) - 268.8Kb


MySQL Enterprise Backup 8.0 Release Notes  /  Changes in MySQL Enterprise Backup 8.0.26 (2021-07-20, General Availability)

Changes in MySQL Enterprise Backup 8.0.26 (2021-07-20, General Availability)

MySQL Enterprise Backup 8.0.26 is the latest release for MySQL Enterprise Backup. It only supports MySQL Server 8.0.26. 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.

Packaging Notes

  • Binary packages that include curl rather than linking to the system curl library have been upgraded to use curl 7.77.0.

Functionality Added or Changed

  • Unnecessary single-table locks have been removed from backup operations. This allows performance improvement for backups that include many small tables. (Bug #32866300)

  • The --free-os-buffers option can now take an argument, which tells mysqlbackup how to utilize posix_fadvise() (on supported platforms) for reducing the impact of mysqlbackup on the system performance. See the option description of --free-os-buffers for details. (Bug #32856108)

  • Performance for backup operations that take place in parallel with DDL operations happening on the server is now improved by removing some unnecessary steps in the operations. (Bug #32855050)

  • mysqlbackup now supports the keyring components on MySQL Servers: InnoDB tables encrypted by utilizing the component_keyring_file and component_keyring_encrypted_file can now be backed up and restored by mysqlbackup. See Working with Encrypted InnoDB Tablespaces for details.

Bugs Fixed

  • mysqlbackup quit unexpectedly during a backup operation if the server had enabled redo and undo log encryption and the system variable --innodb-page-size had a non-default value. (Bug #32845253)

  • The name of a log file created by mysqlbackup should be in the format of MEB_timestamp_operation.log, but the operation was missing in the filename. (Bug #32798284)

  • During a backup operation involving encrypted InnoDB tables, the size of the decrypted InnoDB tablespace key file was not included in the log message for the decryption. (Bug #32787420)

  • After upgrading from MySQL Enterprise Backup 8.0.18 or earlier, performance degradation was observed for large backup jobs involving more than 20,000 tables. That was caused by a number of different issues, which have been corrected by this fix. (Bug #32768465)

  • An incremental backup using page tracking left a temporary file on the server's data directory. With this fix, the file is deleted at the end of the operation. (Bug #32666435)

  • An incremental backup using page tracking failed if the server had a multi-file system tablespace that contained changed pages. (Bug #32580968)

  • There were sporadic failures of backups involving encrypted InnoDB tables with the error "The encrypted table . . . is not initialized." This was caused by deferred flushing of the tablespace headers. This patch fixes the issue by enforcing timely flushing of the tables. (Bug #32495740)

  • After an encrypted InnoDB table was restored from a TTS backup, a subsequent backup operation that included the restored table failed with the complaint that the table seemed corrupted. (Bug #32250682)

  • A TTS backup took a long time to finish, even if it involved only a small amount of data. This was because mysqlbackup did not query for table information in an efficient way, and this patch corrects the issue. (Bug #30481117)