The following is a very brief outline of the steps performed by mysqlbackup when it creates a backup. It does not include every single step taken by mysqlbackup, and the description only represents a very general case—the process can look quite different, depending on the backup options you use (especially with some of the options described in Section 20.10, “Performance / Scalability / Capacity Options” and Section 20.16, “Options for Special Backup Types”). This description only applies to MySQL Enterprise Backup 8.0.16 and later.
In general, this is what happens when you run a backup operation with mysqlbackup:
The InnoDB data files, redo log, binary log, and relay log files (except for the log files currently in use) are being copied into the backup, while the database server operates as usual.
The data and the structures of the InnoDB tables might have changed during this period; so, some of the following steps are for making sure those changes are captured in the backup.
A backup lock is applied on the server instance. It blocks DDL operations (except for those on user-created temporary tables), but not DML operations (except for those not captured by the binary log, like administrative changes to the database) on InnoDB tables. Most read and write activities on the database are still allowed. With this lock applied, mysqlbackup scans for InnoDB tables that have been modified by DDL operations since step 1, and make changes to the backup accordingly.
FLUSH TABLESstatement is applied on all non-InnoDB tables (for release 8.0.18 and later, only on non-InnoDB tables that are to be included in the backup ), after which any non-InnoDB tables relevant to the backup are copied.
tbl_name [, tbl_name]... WITH READ LOCK
This step is skipped if no user-created non-InnoDB tables exist on the database.
A brief blocking of logging activities on the server is applied, for mysqlbackup to collect logging-related information like the current InnoDB LSN, binary log position, GTID, replication source or replica status, and so on.
The read lock on the non-InnoDB tables is released.
Using information from step 4 above, the relevant portion of the binary or relay log file currently in use is copied. This ensures that all recent changes to the InnoDB tables since step 1 are captured in the backup, so they can be applied later to the raw backup data to bring the restored server to a consistent state.
The backup lock on the server instance is released. The database now returns to its normal operations.
The redo log files not yet copied before, as well as all the metadata files for the backup, are copied or created.
The backup operation is completed, and mysqlbackup returns success.