Please refer to the MySQL Enterprise Backup 8.0 Release Notes for a list of fixed bugs for mysqlbackup. Here is a list of limitations of MySQL Enterprise Backup:
In some cases, backups of non-transactional tables such as
MyISAMtables could contain additional uncommitted data. If autocommit is turned off, and both
InnoDBtables and non-transactional tables are modified within the same transaction, data can be written to the non-transactional table before the binary log position is updated. The binary log position is updated when the transaction is committed, but the non-transactional data is written immediately. If the backup occurs while such a transaction is open, the backup data contains the updates made to the non-transactional table.
enginescolumn in the
mysql.backup_historytable does not correctly reflect the storage engines of the backed-up databases.
Hot backups for large databases with heavy writing workloads (say, in the order of gigabytes per minute) can take a very long time to complete due to the huge redo log files that are generated on the server while the backup is running. However, when it is a relatively small subset of tables in the database that are being modified frequently, the Optimistic Backup feature can be used to improve performance and reduce backup size, as well as backup and recovery times. See Section 4.3.6, “Making an Optimistic Backup” for details.
While it is possible to backup to or restore from a Network Attached Storage (NAS) device using MySQL Enterprise Backup, due to networking issues that might arise, the consistency of the backups and the performance of the backup or restore operations might be compromised.
When creating a backup using transportable tablespace (TTS) for a server containing tables with a mix of the Antelope and Barracuda file formats, do not apply full locking on the tables (that is, do not specify
--use-tts=with-full-locking). Instead, just specify
--use-tts=with-minimum-locking, both of which will apply minimum locking to the tables.
Backup of a partitioned table using transportable tablespace (TTS) would fail when any (or all) of its partitions were created in a shared tablespace.
Restoring a partitioned table backed up using transportable tablespace (TTS), even when the
--forceoption is used, would fail if any of the partitions was created outside of the backed-up server's data directory.
If a table containing full-text search (FTS) index is backed up using transportable tablespace (TTS), after it is restored, the FTS index will be corrupted. Users will need to recreate the index with the following command:
mysql> ALTER TABLE mytable ENGINE = INNODB;
Then, check that there are no more errors with the table:
mysql> CHECK TABLE mytable;
MySQL Enterprise Backup does not include the
.pemfiles from the server into the backup. The files are part of the server instance when SSL connections are enabled.
During a backup process, if a
CREATE INDEXstatement with
ALGORITHM = INPLACEis issued when the backup process is going on, because the statement will not go into the redo log of the MySQL server (see Sorted Index Builds for details), it cannot be recorded in the backup, and the index will not be recreated by mysqlbackup when the backup is restored.
When a file of an unrecognized file type exists under a subdirectory in the server's data directory, it will be backed up by mysqlbackup unless the
--only-known-file-typesoption is used. However, if the name of the file does not have an extension, it will cause mysqlbackup to throw an error when it tries to restore the backup to a server.
Cloud operations by MySQL Enterprise Backup are not supported on macOS or Windows platforms, and also on Linux platforms when generic Linux builds are used for both the server and MySQL Enterprise Backup (i.e., when both the server and MySQL Enterprise Backup have been installed using generic Linux tarballs).
Backup operations fail if the server has been started with
Backup operations may fail if checksums for redo log pages are disabled (i.e., if
0) on the server.
For MySQL Enterprise Backup 8.0.19 and later: It is safe to have DDL operations (CREATE TABLE, RENAME TABLE, DROP TABLE, ALTER TABLE, and operations that map to ALTER TABLE like CREATE INDEX) happening on the server in parallel with a backup operation as long as:
The tables involved exist in their own tablespaces, instead of being in the system tablespace or some general tablespaces.
These server features have not been applied to the tables involved:
The backup is not taken with the following
A compressed directory backup fails when a general tablespace bears the same basename as the database's system tablespace (usually
ibdata1) and exists in the same directory with it (usually the server's data directory). A compressed single-file backup created under the same situation will be corrupted, and cannot be restored. To avoid the problem, the server administrator should not put into the same directory the system tablespace and a general tablespace of the same basename; if that is unavoidable, do not perform a compressed backup for the database.
When working with a replication set up whose source server also belongs to a separate Group Replication setup, over time, create backups consistently either from the source or the replica, but not from both. Otherwise, there will be conflicts between the
idvalues generated generated by the source and the replica, causing backups to fail.
A backup fails if the name of any database is the same as the name of any undo tablespace. For backups to be successful, the database administrator should avoid giving any database and undo tablespace the same name (for example, using the default undo tablespace name
undo_001to name a database), or the database should be renamed before a backup.