This section lists some common questions about MySQL Enterprise Backup, with answers and pointers to further information.
A.1: Does MySQL Enterprise Backup work with MySQL Server version
A.2: What is the big
ibdatafile that is in all the backups?
A.3: Can I back up non-InnoDB data with MySQL Enterprise Backup?
A.4: What happens if the apply-log step is interrupted?
A.5: Why is the option
A.6: Can I back up a database on one OS platform and restore it on another one using MySQL Enterprise Backup?
A.7: What if I have included the binary log or relay log in my backup but do not want to restore it?
Questions and Answers
See Section C.3, “Compatibility with MySQL Versions” for details of compatibility between different releases of MySQL Enterprise Backup and MySQL Server.
You might find your backup data taking more space than
expected because of a large file with a name such as
ibdata1. This file represents the InnoDB
tablespace, which grows but never shrinks, and is
included in every full and incremental backup. To reduce the
space taken up by this file in your backup data:
After doing a full backup, do a succession of incremental backups, which take up less space. The
ibdata1file in the incremental backups is typically much smaller, containing only the portions of the system tablespace that changed since the full backup.
Set the configuration option
innodb_file_per_table=1before creating your biggest or most active InnoDB tables. Those tables are split off from the system tablespaces into separate
.ibdfiles, which are more flexible in terms of freeing disk space when dropped or truncated, and can be individually included or excluded from backups.
If your system tablespace is very large because you created a high volume of InnoDB data before turning on the
innodb_file_per_tablesetting, you might use mysqldump to dump the entire instance, then turn on
innodb_file_per_tablebefore re-creating it, so that all the table data is kept outside the system tablespace.
While MySQL Enterprise Backup can back up non-InnoDB data
(like MYISAM tables), the MySQL server to be backed up must
support InnoDB (i.e., the backup process will fail if the
server was started up with the
option), and the server must contain at least one InnoDB
If mysqlbackup is interrupted during the
the backup data is OK. The file operations performed by those
options can be performed multiple times without harming the
consistency of the backup data. Just run the same
mysqlbackup command again, and when it
completes successfully, all the necessary changes are present
in the backup data.
When you specify the
--defaults-file option, it
must be the first option after the name of the command.
Otherwise, the error message makes it look as if the option
name is not recognized.
See Section C.2, “Cross-Platform Compatibility” for details.
If you want to skip the restore of the binary log, relay log,
or both during a restore, use the
--skip-relaylog option, or
both with your