mariabackup Options

You are viewing an old version of this article. View the current version here.

The following mariabackup options are available:

Option                                              Description
--backupTake backup to target-dir.
--binlog-info[=name]This option controls how XtraBackup should retrieve server's binary log coordinates corresponding to the backup. Possible values are OFF, ON, LOCKLESS and AUTO. See the XtraBackup manual for more information. One of: off, lockless, on, auto
--compress[=name]Compress individual backup files using the specified compression algorithm. Currently the only supported algorithm is 'quicklz'. It is also the default algorithm, i.e. the one used when --compress is used without an argument.
--compress-threads=#Number of threads for parallel data compression. The default value is 1.
--compress-chunk-size=#Size of working buffer(s) for compression threads in bytes. The default value is 64K.
--close-filesdo not keep files opened. Use at your own risk.
--copy-backCopy all the files in a previously made backup from the backup directory to their original locations.
--core-fileWrite core on fatal signals
--databases=namefiltering by list of databases.
--databases-exclude=nameExcluding databases based on name, Operates the same way as --databases, but matched names are excluded from backup. Note that this option has a higher priority than --databases.
--databases-file=namefiltering by list of databases in the file.
-h, --datadir=namePath to the database root.
--debug-sleep-before-unlock=#This is a debug-only option used by the XtraBackup test suite.
--decompressDecompresses all files with the .qp extension in a backup previously made with the --compress option.
--defaults-extra-file=#Read this file after the global files are read.
--defaults-file=#Only read default options from the given file #.
--defaults-group=namedefaults group in config file (default "mysqld").
--exportcreate files to import to another database when prepare.
--extra-lsndir=name(for --backup): save an extra copy of the xtrabackup_checkpoints file in this directory.
--force-non-empty-directoriesThis option, when specified, makes --copy-back or --move-back transfer files to non-empty directories. Note that no existing files will be overwritten. If --copy-back or --nove-back has to copy a file from the backup directory which already exists in the destination directory, it will still fail with an error.
--ftwrl-wait-query-type=nameThis option specifies which types of queries are allowed to complete before innobackupex will issue the global lock. Default is all.. One of: ALL, UPDATE, SELECT
--ftwrl-wait-timeout=#This option specifies time in seconds that innobackupex should wait for queries that would block FTWRL before running it. If there are still such queries when the timeout expires, innobackupex terminates with an error Default is 0, in which case innobackupex does not wait for queries to complete and starts FTWRL immediately.
--ftwrl-wait-threshold=#This option specifies the query run time threshold which is used by innobackupex to detect long-running queries with a non-zero value of --ftwrl-wait-timeout. FTWRL is not started until such long-running queries exist. This option has no effect if --ftwrl-wait-timeout is 0. Default value is 60 seconds.
--galera-infoThis options creates the xtrabackup_galera_info file which contains the local node state at the time of the backup. Option should be used when performing the backup of Percona-XtraDB-Cluster. Has no effect when backup locks are used to create the backup.
--history[=name]This option enables the tracking of backup history in the PERCONA_SCHEMA.xtrabackup_history table. An optional history series name may be specified that will be placed with the history record for the current backup being taken.
-H, --host=nameThis option specifies the host to use when connecting to the database server with TCP/IP. The option accepts a string argument. See mysql --help for details.
--incremental-basedir=name(for --backup): copy only .ibd pages newer than backup at specified directory.
--incremental-dir=name(for --prepare): apply .delta files and logfile in the specified directory.
--incremental-force-scanPerform a full-scan incremental backup even in the presence of changed page bitmap data
--incremental-history-name=nameThis option specifies the name of the backup series stored in the PERCONA_SCHEMA.xtrabackup_history history record to base an incremental backup on. Xtrabackup will search the history table looking for the most recent (highest innodb_to_lsn), successful backup in the series and take the to_lsn value to use as the starting lsn for the incremental backup. This will be mutually exclusive with --incremental-history-uuid, --incremental-basedir and --incremental-lsn. If no valid lsn can be found (no series by that name, no successful backups by that name) xtrabackup will return with an error. It is used with the --incremental option.
--incremental-history-uuid=nameThis option specifies the UUID of the specific history record stored in the PERCONA_SCHEMA.xtrabackup_history to base an incremental backup on. --incremental-history-name, --incremental-basedir and --incremental-lsn. If no valid lsn can be found (no success record with that uuid) xtrabackup will return with an error. It is used with the --incremental option.
--incremental-lsn=name(for --backup): copy only .ibd pages newer than specified LSN 'high:low'. ATTENTION: If a wrong LSN value is specified, it is impossible to diagnose this, causing the backup to be unusable. Be careful!
--innodb[=name]Ignored option for MySQL option compatibility
--innodb-adaptive-hash-indexEnable InnoDB adaptive hash index (enabled by default). Disable with --skip-innodb-adaptive-hash-index (Defaults to on; use --skip-innodb-adaptive-hash-index to disable.)
--innodb-autoextend-increment=#Data file autoextend increment in megabytes
--innodb-buffer-pool-size=#The size of the memory buffer InnoDB uses to cache data and indexes of its tables.
--innodb-data-file-path=namePath to individual files and their sizes.
--innodb-data-home-dir=nameThe common part for InnoDB table spaces.
--innodb-doublewriteEnable InnoDB doublewrite buffer during --prepare.
--innodb-io-capacity[=#]Number of IOPs the server can do. Tunes the background IO rate
--innodb-file-io-threads=#Number of file I/O threads in InnoDB.
--innodb-read-io-threads=#Number of background read I/O threads in InnoDB.
--innodb-write-io-threads=#Number of background write I/O threads in InnoDB.
--innodb-file-per-tableStores each InnoDB table to an .ibd file in the database dir.
--innodb-flush-method=nameWith which method to flush data.
--innodb-log-buffer-size=#The size of the buffer which InnoDB uses to write log to the log files on disk.
--innodb-log-file-size=#Ignored for mysqld option compatibility
--innodb-log-files-in-group=#Ignored for mysqld option compatibility
--innodb-log-group-home-dir=namePath to InnoDB log files.
--innodb-max-dirty-pages-pct=#Percentage of dirty pages allowed in bufferpool.
--innodb-open-files=#How many files at the maximum InnoDB keeps open at the same time.
--innodb-use-native-aioUse native AIO if supported on this platform.
--innodb-page-size=#The universal page size of the database.
--innodb-buffer-pool-filename=nameIgnored for mysqld option compatibility
--debug-sync=nameDebug sync point. This is only used by the xtrabackup test suite
--innodb-checksum-algorithm=nameThe algorithm InnoDB uses for page checksumming. [CRC32, STRICT_CRC32, INNODB, STRICT_INNODB, NONE, STRICT_NONE]. One of: crc32, strict_crc32, innodb, strict_innodb, none, strict_none
--innodb-undo-directory=nameDirectory where undo tablespace files live, this path can be absolute.
--innodb-undo-tablespaces=#Number of undo tablespaces to use.
--innodb-encrypt-logshould log be encrypted.
--innodb-log-checksumsWhether to require checksums for InnoDB redo log blocks (Defaults to on; use --skip-innodb-log-checksums to disable.)
--kill-long-queries-timeout=#This option specifies the number of seconds innobackupex waits between starting FLUSH TABLES WITH READ LOCK and killing those queries that block it. Default is 0 seconds, which means innobackupex will not attempt to kill any queries.
--kill-long-query-type=nameThis option specifies which types of queries should be killed to unblock the global lock. Default is "all".. One of: ALL, UPDATE, SELECT
--log[=name]Ignored option for MySQL option compatibility
--log-bin[=name]Base name for the log sequence
--log-copy-interval=#time interval between checks done by log copying thread in milliseconds (default is 1 second).
--move-backMove all the files in a previously made backup from the backup directory to the actual datadir location. Use with caution, as it removes backup files.
--no-backup-locksThis option controls if backup locks should be used instead of FLUSH TABLES WITH READ LOCK on the backup stage. The option has no effect when backup locks are not supported by the server. This option is enabled by default, disable with --no-backup-locks.
--no-defaultsDon't read default options from any option file.
--no-lockUse this option to disable table lock with "FLUSH TABLES WITH READ LOCK". Use it only if ALL your tables are InnoDB and you DO NOT CARE about the binary log position of the backup. This option shouldn't be used if there are any DDL statements being executed or if any updates are happening on non-InnoDB tables (this includes the system MyISAM tables in the mysql database), otherwise it could lead to an inconsistent backup. If you are considering to use --no-lock because your backups are failing to acquire the lock, this could be because of incoming replication events preventing the lock from succeeding. Please try using --safe-slave-backup to momentarily stop the replication slave thread, this may help the backup to succeed and you then don't need to resort to using this option.
--no-version-checkThis option disables the version check which is enabled by the --version-check option.
--open-files-limit=#the maximum number of file descriptors to reserve with setrlimit().
--parallel=#Number of threads to use for parallel datafiles transfer. The default value is 1.
-p, --password=nameThis option specifies the password to use when connecting to the database. It accepts a string argument. See mysql --help for details.
--plugin-dir=nameServer plugin directory .Only used during --prepare phase, to load encryption plugin. Default value is the server's --plugin-dir as of backup time. It is stored in backup-my.cnf
--plugin-load=nameencrypton plugin to load. Only used during --prepare phase, to load encryption plugin. Default value is the server's --plugin-load as of backup time. It is stored in backup-my.cnf
-P, --port=#This option specifies the port to use when connecting to the database server with TCP/IP. The option accepts a string argument. See mysql --help for details.
--prepareprepare a backup for starting mysql server on the backup.
--print-defaultsPrint the program argument list and exit.
--print-paramprint parameter of mysqld needed for copyback.
--rsyncUses the rsync utility to optimize local file transfers. When this option is specified, innobackupex uses rsync to copy all non-InnoDB files instead of spawning a separate cp for each file, which can be much faster for servers with a large number of databases or tables. This option cannot be used together with --stream.
--safe-slave-backupStop slave SQL thread and wait to start backup until Slave_open_temp_tables in "SHOW STATUS" is zero. If there are no open temporary tables, the backup will take place, otherwise the SQL thread will be started and stopped until there are no open temporary tables. The backup will fail if Slave_open_temp_tables does not become zero after --safe-slave-backup-timeout seconds. The slave SQL thread will be restarted when the backup finishes.
--safe-slave-backup-timeout=#How many seconds --safe-slave-backup should wait for Slave_open_temp_tables to become zero. (default 300)
--secure-authRefuse client connecting to server if it uses old (pre-4.1.1) protocol. (Defaults to on; use --skip-secure-auth to disable.)
--slave-infoThis option is useful when backing up a replication slave server. It prints the binary log position and name of the master server. It also writes this information to the "xtrabackup_slave_info" file as a "CHANGE MASTER" command. A new slave for this master can be set up by starting a slave server on this backup and issuing a "CHANGE MASTER" command with the binary log position saved in the "xtrabackup_slave_info" file.
-S, --socket=nameThis option specifies the socket to use when connecting to the local database server with a UNIX domain socket. The option accepts a string argument. See mysql --help for details.
--stream=nameStream all backup files to the standard output in the specified format.Supported format is 'xbstream'.
--tables=namefiltering by regexp for table names.
--tables-exclude=namefiltering by regexp for table names. Operates the same way as --tables, but matched names are excluded from backup. Note that this option has a higher priority than --tables.
--tables-file=nameiltering by list of the exact database.table name in the file.
--target-dir=namedestination directory
--throttle=#limit count of IO operations (pairs of read&write) per second to IOS values (for '--backup')
-t, --tmpdir=namePath for temporary files. Several paths may be specified, separated by a colon (:), in this case they are used in a round-robin fashion.
--use-memory=#The value is used instead of buffer_pool_size
-u, --user=nameThis option specifies the MySQL username used when connecting to the server, if that's not the current user. The option accepts a string argument. See mysql --help for details.
-v, --versionprint xtrabackup version information

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.