Buy Percona ServicesBuy Now!

The xtrabackup Option Reference

This page documents all of the command-line options for the xtrabackup binary.



Print the program argument list and exit. Must be given as the first option on the command-line.


Don’t read default options from any option file. Must be given as the first option on the command-line.


Only read default options from the given file. Must be given as the first option on the command-line. Must be a real file; it cannot be a symbolic link.


Read this file after the global files are read. Must be given as the first option on the command-line.


This option causes only the redo stage to be performed when preparing a backup. It is very important for incremental backups.


Make a backup and place it in --target-dir. See Creating a backup.


This option is not currently implemented. To create the InnoDB log files, you must prepare the backup twice at present.


The source directory for the backup. This should be the same as the datadir for your MySQL server, so it should be read from my.cnf if that exists; otherwise you must specify it on the command line.


Create files necessary for exporting tables. See Exporting and Importing Tables.


When creating an incremental backup, this is the directory containing the full backup that is the base dataset for the incremental backups.


When preparing an incremental backup, this is the directory where the incremental backup is combined with the full backup to make a new full backup.


When creating an incremental backup, you can specify the log sequence number (LSN) instead of specifying --incremental-basedir. For databases created by MySQL and Percona Server 5.0-series versions, specify the LSN as two 32-bit integers in high:low format. For databases created in 5.1 and later, specify the LSN as a single 64-bit integer.


There is a large group of InnoDB options that are normally read from the my.cnf configuration file, so that xtrabackup boots up its embedded InnoDB in the same configuration as your current server. You normally do not need to specify these explicitly. These options have the same behavior that they have in InnoDB or XtraDB. They are as follows:


Makes xtrabackup not copy data files, and output the contents of the InnoDB log files to STDOUT until the --suspend-at-end file is deleted. This option enables --suspend-at-end automatically.


Makes xtrabackup perform recovery on a backup created with --backup, so that it is ready to use. See preparing a backup.


Makes xtrabackup print out parameters that can be used for copying the data files back to their original locations to restore them. See Scripting Backups With xtrabackup.


Causes xtrabackup to scan the specified data files and print out index statistics.


Causes xtrabackup to create a file called xtrabackup_suspended in the --target-dir. Instead of exiting after copying data files, xtrabackup continues to copy the log file, and waits until the xtrabackup_suspended file is deleted. This enables xtrabackup and other programs to coordinate their work. See Scripting Backups With xtrabackup.


A file containing one table name per line, in databasename.tablename format. The backup will be limited to the specified tables. See Scripting Backups With xtrabackup.


A regular expression against which the full tablename, in databasename.tablename format, is matched. If the name matches, the table is backed up. See partial backups.


This option specifies the destination directory for the backup. If the directory does not exist, xtrabackup creates it. If the directory does exist and is empty, xtrabackup will succeed. xtrabackup will not overwrite existing files, however; it will fail with operating system error 17, file exists.

Note that for --backup, if this option is a relative path, it is interpreted as being relative to the --datadir, not relative to the current working directory from which xtrabackup is executed. For --prepare, relative paths are interpreted as being relative to the current working directory.


This option limits --backup to the specified number of read+write pairs of operations per second. See throttling a backup.


This option is currently not used for anything except printing out the correct tmpdir parameter when --print-param is used.


This option affects how much memory is allocated for preparing a backup with --prepare, or analyzing statistics with --stats. Its purpose is similar to innodb_buffer_pool_size. It does not do the same thing as the similarly named option in Oracle’s InnoDB Hot Backup tool. The default value is 100MB, and if you have enough available memory, 1GB to 2GB is a good recommended value.


This option specifies the number of threads to use to copy multiple data files concurrently when creating a backup. The default value is 1 (i.e., no concurrent transfer).

Currently, the option only works for local backups.


This option prints xtrabackup version and exits.

Table Of Contents

Previous topic

xtrabackup Exit Codes

Next topic

The tar4ibd Binary

Visit Percona Store

General Inquiries

For general inquiries, please send us your question and someone will contact you.