Index of files created by Percona XtraBackup

  • Information related to the backup and the server

    • backup-my.cnf

      This file contains information to start the mini instance of InnoDB during the --apply-log. This is NOT a backup of original my.cnf. The InnoDB configuration is read from the file backup-my.cnf created by innobackupex when the backup was made. innobackupex --apply-log uses InnoDB configuration from backup-my.cnf by default, or from innobackupex --defaults-file, if specified. InnoDB configuration in this context means server variables that affect data format, i.e. innodb_page_size, innodb_log_block_size, etc. Location-related variables, like innodb_log_group_home_dir or innodb_data_file_path are always ignored by innobackupex --apply-log, so preparing a backup always works with data files from the backup directory, rather than any external ones.

    • xtrabackup_checkpoints

      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_checkpoints after taking a full backup:

      backup_type = full-backuped
      from_lsn = 0
      to_lsn = 15188961605
      last_lsn = 15188961605
      

      Example of the xtrabackup_checkpoints after taking an incremental backup:

      backup_type = incremental
      from_lsn = 15188961605
      to_lsn = 15189350111
      last_lsn = 15189350111
      
    • xtrabackup_binlog_info

      The binary log file used by the server and its position at the moment of the backup. Result of the SHOW MASTER STATUS.

    • xtrabackup_binlog_pos_innodb

      The binary log file and its current position for InnoDB or XtraDB tables.

    • xtrabackup_binary

      The xtrabackup binary used in the process.

    • xtrabackup_logfile

      Contains data needed for running the: --apply-log. The bigger this file is the --apply-log process will take longer to finish.

    • <table_name>.delta.meta

      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
      
    • <table_name>.ibd.pmap

      This file contains ranges of skipped secondary index pages. These files are created only when doing the compact backup. The file format is a series of 2-value tuples, with each value being a 4-byte page offset corresponding to the first and the last endpoints of skipped ranges, respectively.

  • Information related to the replication environment (if using the --slave-info option):

    • xtrabackup_slave_info

      The CHANGE MASTER statement needed for setting up a slave.

  • Information related to the Galera and Percona XtraDB Cluster (if using the --galera-info option):

    • xtrabackup_galera_info

      Contains the values of status variables wsrep_local_state_uuid and wsrep_last_committed.

Percona XtraBackup
Call Us
+1-888-316-9775 (USA - Sales)
+1-208-473-2904 (USA - Sales)
+44-208-133-0309 (UK - Sales)
0-800-051-8984 (UK - Sales)
0-800-181-0665 (GER - Sales)
+1-877-862-4316 (Emergency)
+1-855-55TRAIN (Training)
+1-925-271-5054 (Training)

Previous topic

Glossary

Next topic

Trademark Policy

This Page



© Copyright 2009-2014, Percona LLC and/or its affiliates.
Except where otherwise noted, this documentation is licensed under the following license:
CC Attribution-ShareAlike 2.0 Generic
Created using Sphinx 1.1.3.
This documentation is developed in Launchpad as part of the Percona XtraBackup source code.
If you spotted innacuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.
]]>