Incremental backup. For usage details, see Example: Making an Incremental Backup of InnoDB Tables.

Support for the Barracuda file format of InnoDB. MySQL Enterprise Backup can now backup tables that use recent InnoDB features such as table compression and the dynamic row format.

The innobackup or mysqlbackup command could create an orphaned table in the backup directory. The file mysql/ibbackup_binlog_marker.ibd was created in the backup directory, but not mysql/ibbackup_binlog_marker.frm. The resulting table mysql.ibbackup_binlog_marker could not be dropped or re-created, which could prevent subsequent backups from succeeding. This condition could occur when a partial backup was created with the --databases option, and the database had multiple tablespaces from the setting --innodb-file-per-table=1. Now, the .frm file for this internally produced table is copied into the backup without the table being specified as part of the --databases argument list. (Bug #54454)