MySQL Enterprise Backup 4.0 Release Notes  /  Changes in MySQL Enterprise Backup 4.0.0 (2015-10-21)

Changes in MySQL Enterprise Backup 4.0.0 (2015-10-21)

Functionality Added or Changed

Bugs Fixed

  • After an apply-incremental-backup operation on a full backup, mysqlbackup printed to the output stream and the message log file the old instead of the updated binary log position. (Bug #21822086)

  • When a backup took a long time to perform and the binary logs were rotated in the middle of the process, mysqlbackup lost track of the binary log files it was copying, skipping the second last log file and attempting to copy the last one twice; that resulted in a file creation error, at which point mysqlbackup exited without releasing its lock on the tables in the database. With this fix, all binary log files are now copied properly, and the lock on the tables is released at the end of the backup process as usual. (Bug #20971763)

  • When restoring an incremental backup image, if the binary log in the backup was larger than 16MB, the restored binary log would become corrupted, as mysqlbackup kept overwriting the same 16-MB file again and again with binary log contents. With this fix, the binary log is now correctly restored and has the same size as it did on the backed-up server. (Bug #20915642)

  • When the --password option was used without an argument with the copy-back-and-apply-log command, mysqlbackup did not prompt user for a password, but either took the password from the defaults files, or took it to be an empty string when no value was specified in the defaults files. (Bug #20657939)