Functionality Added or Changed
MySQL Enterprise Backup has a new
--on-disk-full command line option.
mysqlbackup could hang when the disk became
full, rather than detecting the low space condition.
mysqlbackup now monitors disk space when
running backup commands, and users can now specify the action to
take at a disk-full condition with the
--on-disk-full option. See
Section 4.1.11, “Performance / Scalability / Capacity Options” for details.
(Bug #13817288, Bug #13804407)
MySQL Enterprise Backup has a new progress report feature, which
periodically outputs short progress indicators on its operations
to user-selected destinations (for example,
stderr, a file, or
other choices). This feature is controlled by the new progress
report options described in
Section 4.1.12, “Progress Report Options”.
MySQL Server failed to start after a backup was restored if there had been online DDL transactions on partitioned tables during the time of backup. (Bug #16924499)
apply-incremental-backup might fail
with an assertion error if the InnoDB tables being backed up
were created in Barracuda format and with their
different from the
innodb_page_size. This fix
ensures that different
are handled properly during incremental backup and
Perform incremental backups with MySQL Enterprise Backup 3.8.2
instead of any older version to ensure a successful
(Bug #16423621, Bug #16842291)
If a table was renamed following a full backup, a subsequent
incremental backup could copy the
with the new name, but not the associated
.ibd file with the new name. After a restore,
the InnoDB data dictionary could be in an inconsistent state.
This issue primarily occurred if the table was not changed
between the full backup and the subsequent incremental backup.
After a full backup, if a table was renamed and modified,
apply-incremental-backup would crash
when run on the backup directory.
The value of the binary log position in
backup_variables.txt could be different from
the output displayed during the
(This issue did not occur if the backup and apply-log steps were
A backup process might hang when it ran into an LSN mismatch between a data file and the redo log. This fix makes sure the process does not hang and it displays an error message showing the name of the problematic data file. (Bug #14791645)
When using the
--only-innodb-with-frm option, MySQL
Enterprise Backup tried to create temporary files at unintended
locations in the file system, which might cause a failure when,
for example, the user had no write privilege for those
locations. This fix makes sure the paths for the temporary files