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.27 (2021-10-19, General Availability)

Changes in MySQL Enterprise Backup 8.0.27 (2021-10-19, General Availability)

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

Functionality Added or Changed

  • The --verbose option is now synonymous with --trace=1. (Bug #32964563)

  • The --debug option now accepts more arguments for providing various kinds of debugging information. See the option description for --debug for details. (Bug #32964563)

  • It is now possible to create an incremental backup with page tracking with a DDL operation taking place in parallel with the backup. Some limitations apply; see more details here. (Bug #30603944)

Bugs Fixed

  • Backup and restore operations might fail if arguments for the --datadir or --backup_dir options contained symbolic links. (Bug #33134292)

  • During an incremental backup operation, mysqlbackup quit unexpectedly after receiving a segmentation error when the disk was full. This fix adds proper handling for a disk full error. (Bug #33123802)

  • An extract operation for a compressed backup sometimes failed if an undo log truncation had taken place during the time the backup was created. (Bug #33082132)

  • A backup operation failed when backing up tables that used the keyring_hashicorp plugin for InnoDB table encryption. It was because the HashiCorp Vault AppRole authentication secret ID supplied using the --encrypt-password option was obfuscated when sent to the server, and the issue has been fixed by this patch. (Bug #33020080)

    References: This issue is a regression of: Bug #32284801.

  • A restore operation failed when, during the creation of the backup, some operation (for example, renaming) was performed on an external general tablespace. It was because mysqlbackup was copying the tablespace twice to the same location on the target server, and that has been corrected by this fix. (Bug #32934170)