Index of files created by Percona XtraBackup¶
Information related to the backup and the server
This file contains information to start the mini instance of InnoDB during the
xtrabackup --prepare. This is NOT a backup of original
my.cnf. The InnoDB configuration is read from the file
backup-my.cnfcreated by innobackupex when the backup was made.
xtrabackup --prepareuses InnoDB configuration from
backup-my.cnfby default, or from
xtrabackup --defaults-file, if specified. InnoDB configuration in this context means server variables that affect data format, i.e.
innodb_log_block_size, etc. Location-related variables, like
innodb_data_file_pathare always ignored by
xtrabackup --prepare, so preparing a backup always works with data files from the backup directory, rather than any external ones.
The type of the backup (e.g. full or incremental), its state (e.g. prepared) and the LSN range contained in it. This information is used for incremental backups. Example of the
xtrabackup_checkpointsafter taking a full backup:
backup_type = full-backuped from_lsn = 0 to_lsn = 15188961605 last_lsn = 15188961605
Example of the
xtrabackup_checkpointsafter taking an incremental backup:
backup_type = incremental from_lsn = 15188961605 to_lsn = 15189350111 last_lsn = 15189350111
The binary log file used by the server and its position at the moment of the backup. Result of the SHOW MASTER STATUS.
The binary log file and its current position for InnoDB or XtraDB tables.
The xtrabackup binary used in the process.
This file is going to be created when performing the incremental backup. It contains the per-table delta metadata: page size, size of compressed page (if the value is 0 it means the tablespace isn’t compressed) and space id. Example of this file could looks like this:
page_size = 16384 zip_size = 0 space_id = 0
Information related to the replication environment (if using the
CHANGE MASTERstatement needed for setting up a slave.
Information related to the Galera and Percona XtraDB Cluster (if using the
- Contains the values of