This section lists any performance-related features and settings in MySQL Server versions that affect various aspects of the backup process.
Some new MySQL 5.6 features introduce changes in directory layout and file contents for InnoDB tables. Backing up servers that use these features requires MySQL Enterprise Backup 3.8.1 or higher:
innodb_page_size
configuration option.
innodb_undo_directory,
innodb_undo_logs, and
innodb_undo_tablespaces
configuration options.
innodb_checksum_algorithm
configuration option.
DATA DIRECTORY clause of the
CREATE TABLE statement, which
produces a .isl file in
the database directory and stores the
.ibd file in a
user-specified location.
The group commit feature in MySQL 5.6 reduces the frequency of
flush operations for the InnoDB
redo log, relying more on the
binary log to ensure consistency. Because MySQL Enterprise Backup
does not back up or replay transactions from the binary log, the
data from InnoDB tables might correspond to a
time during the backup, before the FLUSH TABLES WITH READ
LOCK phase, while the data from
non-InnoDB tables corresponds to the time when
the FLUSH TABLES WITH READ LOCK phase starts.
See Section D.1, “Changes in MySQL Enterprise Backup 3.8.1 (2013-02-05)” for details on the fixes and enhancements related to these MySQL 5.6 features.

User Comments
Add your own comment.