Backup history and progress information is logged to the mysql.backup_history and mysql.backup_progress tables, so that it can be used by the MySQL Enterprise Monitor product and other tools to easily monitor backup operations. For the details of the backup history table, see Chapter 9, Troubleshooting for MySQL Enterprise Backup.

The combined InnoDB and MyISAM backup functionality of the innobackup command is now available on Windows systems. The former Perl script is rewritten in C/C++ as the mysqlbackup command. This release continues to include the innobackup command, which may be deprecated by the next release. There are also some changes to the syntax as specified in the manual.

A call to posix_fadvise() can be used to reduce the flush cycle of the operating system cache and improve backup performance. This option is set on by default.

The file ibbackup_binlog_info in the backup directory is now updated when an incremental backup is applied, to reflect the updated binlog position and LSN of the full backup. (Bug #57286)

The apply-log step for an incremental backup would fail if the innodb_log_group_home_dir and datadir values specified in the configuration file were not the same. (Bug #57375)