When there were no tables matching the regular expression specified with the
--include-tablesoption during a backup operation, mysqlbackup still created a backup, which contained an empty folder for each database on the server. mysqlbackup now throws an error when
--include-tablesselects no tables to be backed up. (Bug #18114353)
MySQL Enterprise Backup can now backup and restore encrypted InnoDB tables. See Working with Encrypted InnoDB Tables and Options for Working with Encrypted InnoDB Tablespaces for details.
When trying to restore a compressed image backup of a server that had separate undo tablespaces residing in the data directory with the
copy-back-and-apply-logcommand, the operation failed at the apply-log phase, as mysqlbackup could not load the undo tablespaces. (Bug #23583961)
Attempts to restore an image backup from the cloud using the
--skip-binlogoption failed with a “global tail magic mismatch” error. This was because mysqlbackup failed to perform a non-sequential read from the cloud with gaps caused by the skipping of the binary logs. This fix makes sure mysqlbackup can perform such reads. (Bug #23534700)
When a compressed backup was being restored, if the undo logs had been put into separate tablespaces outside of the data directory on the backed up server, they got restored twice, once mistakenly as general tablespaces with the
.ibdextension, and once as undo tablespaces without a file extension. This fix makes sure they are restored normally as undo tablespaces only. (Bug #23179194)
extractoperation for an image backup failed with a checksum mismatch error in cases when, during the backup, an InnoDB tablespace file kept growing in size, and mysqlbackup failed to put the correct file size in its file header. (Bug #22905984)
References: This issue is a regression of: Bug #22613568.
During a mysqlbackup operation on a compressed backup (that is, the
--uncompressoption was used), mysqlbackup, in some situations, wrote to the log file multiple instances of the message “ERROR: InnoDB: file write at offset > 4 GB,” even though the operation was actually successful. (Bug #22733760)
Occasionally, some files were missing from an image backup created by the
--backup-to-imagecommand. It was due to an internal race condition, which this fix eliminates. (Bug #19600687)