The InnoDB system tablespace, containing multiple InnoDB tables and associated indexes.

Because the original files might change while the backup is in progress, the apply-log step applies the same changes to the corresponding backup files.

An InnoDB tablespace, which can be (a) a file-per-table tablespace, containing a single InnoDB table and associated indexes, or (b) a file-per-table external tablespace located outside of the server's data directory, containing a single InnoDB table and associated indexes, or (c) a general tablespace, containing one or more tables and their indexes.

Because the original files might change while the backup is in progress, the apply-log step applies the same changes to the corresponding backup files.

Compressed form of InnoDB data files from the MySQL data directory.

Produced instead of .ibd files in a compressed backup. The ibdata* files representing the InnoDB system tablespace also receive this extension in a compressed backup.

The .ibz files are uncompressed during the apply-log, copy-back, or copy-back-and-apply-log step.

Hold metadata about all MySQL tables.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

MyISAM table data.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

MyISAM index data.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Metadata for CSV tables.

These files are copied unmodified. The backup_history and backup_progress tables created by mysqlbackup use the CSV format, so the backup always includes some files with this extension.

Data for CSV tables.

These files are copied unmodified. The backup_history and backup_progress tables created by mysqlbackup use the CSV format, so the backup always includes some files with this extension.

MERGE storage engine references to other tables.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Trigger parameters.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Trigger namespace information.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Database configuration information.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Definitions for partitioned tables.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

ARCHIVE storage engine table metadata.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

ARCHIVE storage engine table data.

The database is put into a read-only state while these files are copied. These files are copied unmodified.

Records the configuration parameters that specify the layout and other important information about the MySQL data files.

The file is created during a backup, and it contains crucial parameters describing the backed-up data like innodb_data_file_path, innodb_log_file_size, innodb_log_files_in_group, and so on. It might also contain other InnoDB parameters like innodb_data_home_dir and innodb_undo_directory if some of the backup repository options were used during the backup. mysqlbackup uses the parameters stored in this file to understand the structure of the backup and to perform various operations. You might need to supply some of these parameters to mysqlbackup during a restore and to mysqld when you start the target server if the target server and the backup are configured differently. See the discussion in Section 4.2.4, “Restoring a Database” for details.

Records names of the .ibd files and their space IDs during an incremental backup.

This file is created during an incremental backup. During a restore, the information in the file is used to delete the tables from the full backup that has been removed between the time of the full backup and the time of the incremental backup.

A condensed version of the ib_logfile* files from the MySQL data directory.

The InnoDB log files (ib_logfile*) are fixed-size files that are continuously updated during the database's operation. For backup purposes, only the changes that are committed while the backup is in progress are needed. These changes are recorded in ibbackup_logfile, and used to re-create the ib_logfile* files during the apply-log phase.

Created instead of the ibbackup_logfile for incremental backups taken with the --incremental-with-redo-log-only option.

Created in the backup directory by mysqlbackup during the apply-log phase after the initial backup.

These files are not copied from the original data directory, but rather re-created in the backup directory during the apply-log phase after the initial backup, using the changes recorded in the ibbackup_logfile file.

Renamed version of each .isl file from the backed-up server.

A .isl file is created when you specify the location of an InnoDB table using the syntax CREATE TABLE ... DATA DIRECTORY = ... (see Creating Tables Externally for details) or when a table is put into a general tabelspace (only for MySQL 5.7 and after; see general tablespace for details). The .isl file acts like a symbolic link pointing to the tablespace file. The .bl files might or might not be turned back into .isl files during the copy-back or copy-back-and-apply-log operation. If the specified directory does not exist on the server where the backup is restored, mysqlbackup attempts to create it. If the directory cannot be created, the restore operation fails. Thus, if you would like to use the DATA DIRECTORY clause to put tables at different locations or to restore to a server with a different file structure where the corresponding directories cannot be created, edit the .bl files before restoring to point to directories that do exist on the destination server.

When restoring a backup created with transportable tablespaces (TTS), if the directory on the target server pointed to by a .bl file already contains .ibd files, the --force option is required when you restore the backup.

Created by the --with-timestamp option. All the backup files go inside this subdirectory.

Use the --with-timestamp option to easily keep more than one set of backup data under the same main backup directory.

A subdirectory that stores the data files and database subdirectories from the original MySQL instance.

Created under the backup directory by mysqlbackup.

Saved under the datadir directory inside the backup. A copy of the index file on the MySQL server that lists all the used binary log files, with the locations of the binary log files properly updated to point to the files' locations in the backup, is included into the backup as well also under the datadir directory. Use the --skip-binlog option to exclude the binary log from the backup.

For offline backups, use the --log-bin-index option to specify the absolute path of the index file on the MySQL server that lists all the used binary log files, if it is different from the default value of the option, for mysqlbackup to find the binary log files and include them in the backups.

For release 4.1.2 and later: By default, the binary log files and the index file are restored to the same locations they were found on the backed-up server. Use the --log-bin option to specify a different target location for the binary log. Use the --skip-binlog option to skip the restoring of the binary log.

For release 4.1.1 and earlier: The binary log files and the index file are restored to the data directory of the restored server. Use the --skip-binlog option to skip the restoring of the binary log.

The binary log files are compressed and saved with the .bz extension when being included in a compressed backup.

Saved under the datadir directory under the backup directory. A copy of the index file on the replica server that lists all the used relay log files, with the locations of the relay log files properly updated to point to the files' locations in the backup directory, is included into the backup as well, under the datadir directory. Use the --skip-relaylog option to exclude the relay log from the backup.

For offline backup, use the --relay-log-index option to specify the absolute path of the index file on the MySQL server that lists all the used relay log files, if it is different from the default value of the option, for mysqlbackup to find the relay log files and include them in the backups.

For release 4.1.2 and later: By default, the relay log files and the index file are restored to the same locations they were found on the backed-up replica server. Use the --relay-log option to specify a different target location for the relay log. Use the --skip-relaylog option to skip the restoring of the relay log.

For release 4.1.1 and earlier: The relay log files and the index file are restored to the data directory of the restored server. Use the --skip-relaylog option to skip the restoring of the relay log.

The relay log files are compressed and saved with the .bz extension when being included in a compressed backup.

The binary log and relay log files are compressed and saved with the .bz extension when being included in a compressed backup. They are decompressed during a restore.

For a server using the keyring_encrypted_file plugin, the file specified by the keyring_encrypted_file_data option on the server is copied over into the backup with its original name under the meta folder.

For a server using the a keyring plugin other than keyring_encrypted_file, the file is named keyring_kef, saved under the meta folder.

Saved under the datadir directory under the backup directory. For an offline backup, use the--master-info-file and --relaylog-info-file options to specify the absolute paths of the information files, if they are different from the default values of the options, for mysqlbackup to find those files and include them in the backups.

The copying of these files are skipped during a backup or a restore when the --skip-relay-log option is used.

A single-file backup produced by the backup-to-image option, with a name specified by the --backup-image option.

You can move the image file without losing or damaging the contents inside it, then unpack it with mysqlbackup using the extract command and specifying the same image name with the --backup-image option. Although some extra files such as backup-my.cnf and the meta subdirectory are present in the backup directory, these files are also included in the image file and do not need to be moved along with it.

Copied from the database subdirectories under the MySQL data directory.

By default, any unrecognized files in subdirectories under the MySQL data directory are copied to the backup. To omit such files, specify the --only-known-file-types option.

A subdirectory that stores files with metadata about the backup.

Created under the backup directory by mysqlbackup. All files listed below go inside the meta subdirectory.

Holds important information about the backup. For use by mysqlbackup only.

mysqlbackup consults and possibly updates this file during operations after the initial backup, such as the apply-log phase or the restore phase.

Contains the list of all the files (except itself) that are present in the single-file backup produced by the backup-to-image or backup-dir-to-image options. For details about this file, see Section 13.4, “Using the MySQL Enterprise Backup Manifest”.

This file is not modified at any stage once generated.

Lists the command line arguments and environment in which the backup was created. For details about this file, see Section 13.4, “Using the MySQL Enterprise Backup Manifest”.

This file is not modified once it is created. You can prevent this file from being generated by specifying the --disable-manifest option.

Essential metadata for the files and database definitions of the backup data. It also contains details of all the plugins defined on the backed-up server, by which users should make sure the same plugins are defined in the same manner on the target server for restoration. For details about this file, see Section 13.4, “Using the MySQL Enterprise Backup Manifest”.

This file is not modified once created. You can prevent this file from being generated by specifying the --disable-manifest option.

Produced by the --comments or --comments-file option.

The comments are specified by you to document the purpose or special considerations for this backup job.

Signifies the backup came from a server with GTIDs enabled.

GTIDs are a replication feature in MySQL 5.6 and higher. See Replication with Global Transaction Identifiers for details. When you back up a server with GTIDs enabled using mysqlbackup, the file named backup_gtid_executed.sql is created in the meta folder under the backup directory. Edit and execute this file after restoring the backup data on a replica server; see Section 7.1, “Setting Up a New Replica” for details.

Contains values of the backed-up server's global variables that are set to non-default values. Use this file or server-all.cnf to start the target server for restoration.

During a copy-back or copy-back-and-apply-log operation, the server repository options values (e.g., --datadir, --innodb_data_home_dir, etc.) in the file are modified if the command makes changes to them through the command options. However, during an apply-incremental-backup operation, the values already saved in the file take precedence and they are not modified by the option values supplied through the command.

Contains values of all the global variables of the backed-up server. Use this file or server-my.cnf to start the target server for restoration.

During a copy-back or copy-back-and-apply-log operation, the server repository options values (e.g., --datadir, --innodb_data_home_dir, etc.) in the file are modified if the command makes changes to them through the command options. However, during an apply-incremental-backup operation, the values already saved in the file take precedence and they are not modified by the option values supplied through the command.

The file produced on the server when innodb_buffer_pool_dump_at_shutdown (enabled by default on MySQL 5.7.7 and after) or innodb_buffer_pool_dump_now is enabled. It holds the list of tablespace IDs and page IDs of the server's buffer pool.

The actual file name might be different, as it can be configured by the server's system variable innodb_buffer_pool_filename"

With the default setting on MySQL server 5.7.7 and after (innodb_buffer_pool_load_at_startup=ON), the target server, during start up, is going to restore the buffer pool state of the backed up server using this file. See Saving and Restoring the Buffer Pool State for details.