mariadb-backup Options

mariadb-backup was previously called mariabackup.

List of `mariadb-backup` Options

`--apply-log`

Prepares an existing backup to restore to the MariaDB Server. This is only valid in innobackupex mode, which can be enabled with the --innobackupex option.

Files that mariadb-backup generates during --backup operations in the target directory are not ready for use on the Server. Before you can restore the data to MariaDB, you first need to prepare the backup.

In the case of full backups, the files are not point in time consistent, since they were taken at different times. If you try to restore the database without first preparing the data, InnoDB rejects the new data as corrupt. Running mariadb-backup with the --prepare command readies the data so you can restore it to MariaDB Server. When working with incremental backups, you need to use the --prepare command and the --incremental-dir option to update the base backup with the deltas from an incremental backup.

mariadb-backup --innobackupex --apply-log

Once the backup is ready, you can use the --copy-back or the --move-back commands to restore the backup to the server.

`--apply-log-only`

If this option is used when preparing a backup, then only the redo log apply stage are performed, and other stages of crash recovery are ignored. This option is used with incremental backups.

Note: This option is not needed or supported anymore.

`--backup`

Backs up your databases.

Using this command option, mariadb-backup performs a backup operation on your database or databases. The backups are written to the target directory, as set by the --target-dir option.

mariadb-backup --backup 
      --target-dir /path/to/backup \
      --user user_name --password user_passwd

mariadb-backup can perform full and incremental backups. A full backup creates a snapshot of the database in the target directory. An incremental backup checks the database against a previously taken full backup, (defined by the --incremental-basedir option) and creates delta files for these changes.

In order to restore from a backup, you first need to run mariadb-backup with the --prepare command option, to make a full backup point-in-time consistent or to apply incremental backup deltas to base. Then you can run mariadb-backup again with either the --copy-back or --move-back commands to restore the database.

For more information, see Full Backup and Restore and Incremental Backup and Restore.

`--binlog-info`

Defines how mariadb-backup retrieves the binary log coordinates from the server.

--binlog-info[=OFF | ON | LOCKLESS | AUTO]

The --binlog-info option supports the following retrieval methods. When no retrieval method is provided, it defaults to AUTO.

Option

Description

OFF

Disables the retrieval of binary log information

ON

Enables the retrieval of binary log information, performs locking where available to ensure consistency

LOCKLESS

Unsupported option

AUTO

Enables the retrieval of binary log information using ON or LOCKLESS where supported

Using this option, you can control how mariadb-backup retrieves the server's binary log coordinates corresponding to the backup.

When enabled, whether using ON or AUTO, mariadb-backup retrieves information from the binlog during the backup process. When disabled with OFF, mariadb-backup runs without attempting to retrieve binary log information. You may find this useful when you need to copy data without metadata like the binlog or replication coordinates.

mariadb-backup --binlog-info --backup

Currently, the LOCKLESS option depends on features unsupported by MariaDB Server. See the description of the xtrabackup_binlog_pos_innodb file for more information. If you attempt to run mariadb-backup with this option, then it causes the utility to exit with an error.

`--close-files`

Defines whether you want to close file handles.

Using this option, you can tell mariadb-backup that you want to close file handles. Without this option, mariadb-backup keeps files open in order to manage DDL operations. When working with particularly large tablespaces, closing the file can make the backup more manageable. However, it can also lead to inconsistent backups. Use at your own risk.

mariadb-backup --close-files --prepare

`--compress`

This option was deprecated as it relies on the no longer maintained QuickLZ library. It are removed in a future release - versions supporting this function will not be affected. It is recommended to instead backup to a stream (stdout), and use a 3rd party compression library to compress the stream, as described in Using Encryption and Compression Tools With mariadb-backup.

Defines the compression algorithm for backup files.

--compress[=compression_algorithm]

The --compress option only supports the now deprecated quicklz algorithm.

Option

Description

quicklz

Uses the QuickLZ compression algorithm

mariadb-backup --compress --backup

If a backup is compressed using this option, then mariadb-backup will record that detail in the xtrabackup_info file.

`--compress-chunk-size`

Deprecated, for details see the --compress option.

Defines the working buffer size for compression threads.

--compress-chunk-size=#

mariadb-backup can perform compression operations on the backup files before writing them to disk. It can also use multiple threads for parallel data compression during this process. Using this option, you can set the chunk size each thread uses during compression. It defaults to 64K.

mariadb-backup --backup --compress \
     --compress-threads=12 --compress-chunk-size=5M

To further configure backup compression, see the --compress and --compress-threads options.

`--compress-threads`

Deprecated, for details see the --compress option.

Defines the number of threads to use in compression.

--compress-threads=#

mariadb-backup can perform compression operations on the backup files before writing them to disk. Using this option, you can define the number of threads you want to use for this operation. You may find this useful in speeding up the compression of particularly large databases. It defaults to single-threaded.

mariadb-backup --compress --compress-threads=12 --backup

To further configure backup compression, see the --compress and --compress-chunk-size options.

`--copy-back`

Restores the backup to the data directory.

Using this command, mariadb-backup copies the backup from the target directory to the data directory, as defined by the --datadir option. You must stop the MariaDB Server before running this command. The data directory must be empty. If you want to overwrite the data directory with the backup, use the --force-non-empty-directories option.

Bear in mind, before you can restore a backup, you first need to run mariadb-backup with the --prepare option. In the case of full backups, this makes the files point-in-time consistent. With incremental backups, this applies the deltas to the base backup. Once the backup is prepared, you can run --copy-back to apply it to MariaDB Server.

mariadb-backup --copy-back --force-non-empty-directories

Running the --copy-back command copies the backup files to the data directory. Use this command if you want to save the backup for later. If you don't want to save the backup for later, use the --move-back command.

`--core-file`

Defines whether to write a core file.

Using this option, you can configure mariadb-backup to dump its core to file in the event that it encounters fatal signals. You may find this useful for review and debugging purposes.

mariadb-backup --core-file --backup

`--databases`

Defines the databases and tables you want to back up.

--databases="database[.table][ database[.table] ...]"

Using this option, you can define the specific database or databases you want to back up. In cases where you have a particularly large database or otherwise only want to back up a portion of it, you can optionally also define the tables on the database.

mariadb-backup --backup \
      --databases="example.table1 example.table2"

In cases where you want to back up most databases on a server or tables on a database, but not all, you can set the specific databases or tables you don't want to back up using the --databases-exclude option.

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

In innobackupex mode, which can be enabled with the --innobackupex option, the --databases option can be used as described above, or it can be used to refer to a file, just as the --databases-file option can in the normal mode.

`--databases-exclude`

Defines the databases you don't want to back up.

--databases-exclude="database[.table][ database[.table] ...]"

Using this option, you can define the specific database or databases you want to exclude from the backup process. You may find it useful when you want to back up most databases on the server or tables on a database, but would like to exclude a few from the process.

mariadb-backup --backup \
      --databases="example" \
      --databases-exclude="example.table1 example.table2"

To include databases in the backup, see the --databases option option

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--databases-file`

Defines the path to a file listing databases and/or tables you want to back up.

--databases-file="/path/to/database-file"

Format the databases file to list one element per line, with the following syntax:

database[.table]

In cases where you need to back up a number of databases or specific tables in a database, you may find the syntax for the --databases and --databases-exclude options a little cumbersome. Using this option you can set the path to a file listing the databases or databases and tables you want to back up.

For instance, imagine you list the databases and tables for a backup in a file called main-backup.

cat main-backup

example1
example2.table1
example2.table2

mariadb-backup --backup --databases-file=main-backup

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`-h, --datadir`

Defines the path to the database root.

--datadir=PATH

Using this option, you can define the path to the source directory. This is the directory that mariadb-backup reads for the data it backs up. It should be the same as the MariaDB Server datadir system variable.

mariadb-backup --backup -h /var/lib64/mysql

`--debug-sleep-before-unlock`

This is a debug-only option used by the Xtrabackup test suite.

`--decompress`

Deprecated, for details see the --compress option.

This option requires that you have the qpress utility installed on your system.

Defines whether you want to decompress previously compressed backup files.

When you run mariadb-backup with the --compress option, it compresses the subsequent backup files, using the QuickLZ algorithm. Using this option, mariadb-backup decompresses the compressed files from a previous backup.

For instance, run a backup with compression,

mariadb-backup --compress --backup

Then decompress the backup,

mariadb-backup --decompress

You can enable the decryption of multiple files at a time using the --parallel option. By default, mariadb-backup does not remove the compressed files from the target directory. If you want to delete these files, use the --remove-original option.

`--debug-sync`

Defines the debug sync point. This option is only used by the mariadb-backup test suite.

`--defaults-extra-file`

Defines the path to an extra default option file.

--defaults-extra-file=/path/to/config

Using this option, you can define an extra default option file for mariadb-backup. Unlike --defaults-file, this file is read after the default option files are read, allowing you to only overwrite the existing defaults.

mariadb-backup --backup \
      --defaults-file-extra=addition-config.cnf \
      --defaults-file=config.cnf

`--defaults-file`

Defines the path to the default option file.

--defaults-file=/path/to/config

Using this option, you can define a default option file for mariadb-backup. Unlike the --defaults-extra-file option, when this option is provided, it completely replaces all default option files.

mariadb-backup --backup \
     --defaults-file="config.cnf

`--defaults-group`

Defines the option group to read in the option file.

--defaults-group="name"

In situations where you find yourself using certain mariadb-backup options consistently every time you call it, you can set the options in an option file. The --defaults-group option defines what option group mariadb-backup reads for its options.

Options you define from the command-line can be set in the configuration file using minor formatting changes. For instance, if you find yourself perform compression operations frequently, you might set --compress-threads and --compress-chunk-size options in this way:

[mariadb-backup]
compress_threads = 12
compress_chunk_size = 64K

Now whenever you run a backup with the --compress option, it always performs the compression using 12 threads and 64K chunks.

mariadb-backup --compress --backup

See mariadb-backup Overview: Server Option Groups and mariadb-backup Overview: Client Option Groups for a list of the option groups read by mariadb-backup by default.

`--encrypted-backup`

When this option is used with --backup, if mariadb-backup encounters a page that has a non-zero key_version value, then mariadb-backup assumes that the page is encrypted.

Use --skip-encrypted-backup instead to allow mariadb-backup to copy unencrypted tables that were originally created before MySQL 5.1.48.

`--export`

If this option is provided during the --prepare stage, then it tells mariadb-backup to create .cfg files for each InnoDB file-per-table tablespace. These .cfg files are used to import transportable tablespaces in the process of restoring partial backups and restoring individual tables and partitions.

The --export option could require rolling back incomplete transactions that had modified the table. This will likely create a "new branch of history" that does not correspond to the server that had been backed up, which makes it impossible to apply another incremental backup on top of such additional changes. The option should only be applied when doing a --prepare of the last incremental.

mariadb-backup --prepare --export

mariadb-backup did not support the --export option. See MDEV-13466 about that. In earlier versions of MariaDB, this means that mariadb-backup could not create .cfg files for InnoDB file-per-table tablespaces during the --prepare stage. You can still import file-per-table tablespaces without the .cfg files in many cases, so it may still be possible in those versions to restore partial backups or to restore individual tables and partitions with just the .ibd files. If you have a full backup and you need to create .cfg files for InnoDB file-per-table tablespaces, then you can do so by preparing the backup as usual without the --export option, and then restoring the backup, and then starting the server. At that point, you can use the server's built-in features to copy the transportable tablespaces.

`--extra-lsndir`

Saves an extra copy of the xtrabackup_checkpoints and xtrabackup_info files into the given directory.

--extra-lsndir=PATH

When using the --backup command option, mariadb-backup produces a number of backup files in the target directory. Using this option, you can have mariadb-backup produce additional copies of the xtrabackup_checkpoints and xtrabackup_info files in the given directory.

mariadb-backup --extra-lsndir=extras/ --backup

This is especially usefull when using --stream for streaming output, e.g. for compression and/or encryption using external tools in combination with incremental backups, as the xtrabackup_checkpoints file necessary to determine the LSN to continue the incremental backup from is still accessible without uncompressing / decrypting the backup file first. Simply pass in the --extra-lsndir of the previous backup as--incremental-basedir

`--force-non-empty-directories`

Allows --copy-back or --move-back command options to use non-empty target directories.

When using mariadb-backup with the --copy-back or --move-back command options, they normally require a non-empty target directory to avoid conflicts. Using this option with either of command allows mariadb-backup to use a non-empty directory.

mariadb-backup --force-non-empty-directories --copy-back

Bear in mind that this option does not enable overwrites. When copying or moving files into the target directory, if mariadb-backup finds that the target file already exists, it fails with an error.

`--ftwrl-wait-query-type`

Defines the type of query allowed to complete before mariadb-backup issues the global lock.

--ftwrl-wait-query-type=[ALL | UPDATE | SELECT]

The --ftwrl-wait-query-type option supports the following query types. The default value is ALL.

Option

Description

ALL

Waits until all queries complete before issuing the global lock

SELECT

Waits until SELECT statements complete before issuing the global lock

UPDATE

Waits until UPDATE statements complete before issuing the global lock

When mariadb-backup runs, it issues a global lock to prevent data from changing during the backup process. When it encounters a statement in the process of executing, it waits until the statement is finished before issuing the global lock. Using this option, you can modify this default behavior to ensure that it waits only for certain query types, such as for SELECT and UPDATE statements.

mariadb-backup --backup  \
      --ftwrl-wait-query-type=UPDATE

`--ftwrl-wait-threshold`

Defines the minimum threshold for identifying long-running queries for FTWRL.

--ftwrl-wait-threshold=#

When mariadb-backup runs, it issues a global lock to prevent data from changing during the backup process and ensure a consistent record. If it encounters statements still in the process of executing, it waits until they complete before setting the lock. Using this option, you can set the threshold at which mariadb-backup engages FTWRL. When it --ftwrl-wait-timeout is not 0 and a statement has run for at least the amount of time given this argument, mariadb-backup waits until the statement completes or until the --ftwrl-wait-timeout expires before setting the global lock and starting the backup.

mariadb-backup --backup \
     --ftwrl-wait-timeout=90 \
     --ftwrl-wait-threshold=30

`--ftwrl-wait-timeout`

Defines the timeout to wait for queries before trying to acquire the global lock. The global lock refers to BACKUP STAGE BLOCK_COMMIT. The global lock refers to FLUSH TABLES WITH READ LOCK (FTWRL).

--ftwrl-wait-timeout=#

When mariadb-backup runs, it acquires a global lock to prevent data from changing during the backup process and ensure a consistent record. If it encounters statements still in the process of executing, it can be configured to wait until the statements complete before trying to acquire the global lock.

If the --ftwrl-wait-timeout is set to 0, then mariadb-backup tries to acquire the global lock immediately without waiting. This is the default value.

If the --ftwrl-wait-timeout is set to a non-zero value, then mariadb-backup waits for the configured number of seconds until trying to acquire the global lock.

Starting in MariaDB 10.5.3, mariadb-backup will exit if it can't acquire the global lock after waiting for the configured number of seconds. In earlier versions, it could wait for the global lock indefinitely, even if --ftwrl-wait-timeout was set to a non-zero value.

mariadb-backup --backup \
      --ftwrl-wait-query-type=UPDATE \
      --ftwrl-wait-timeout=5

The --ftwrl-wait-timeout option specifies the maximum time that mariadb-backup will wait to obtain the global lock required to begin a consistent backup.

this lock is acquired with BACKUP STAGE BLOCK_COMMIT.

this lock is acquired with FLUSH TABLES WITH READ LOCK (FTWRL).

If the lock cannot be obtained within the configured timeout, the backup process fails.

This option helps avoid failures caused by long running MariaDBueries that block backup locks.

Example Errors

When the timeout is not set appropriately, backups may fail with messages such as:

Unable to obtain lock. Please try again later.

FATAL ERROR: failed to execute query BACKUP STAGE START:
Lock wait timeout exceeded; try restarting transaction

Example Log Excerpt

[00] 2022-02-08 15:43:25 Unable to obtain lock. Please try again later.
[00] 2022-02-08 15:43:25 Error on BACKUP STAGE START query execution
mariabackup: Stopping log copying thread.

Originally, mariadb backup could wait indefinitely for the lock. Starting with the fix for MDEV-20230:

The --ftwrl-wait-timeout option also ensures mariadb backup exits gracefully if the lock cannot be obtained within the timeout period.
This prevents backups from hanging when lock acquisition is blocked by long-running queries.

When to Use

Use --ftwrl-wait-timeout when:

Your workload includes long-running queries (for example, ALTER TABLE or large INSERT batches).
Backups sometimes fail with lock wait timeout errors.
You want mariadb backup to either wait longer for the lock or exit cleanly if it cannot be obtained.

`--galera-info`

Defines whether you want to back up information about a Galera Cluster node's state.

When this option is used, mariadb-backup creates an additional file called xtrabackup_galera_info, which records information about a Galera Cluster node's state. It records the values of the wsrep_local_state_uuid and wsrep_last_committed status variables.

You should only use this option when backing up a Galera Cluster node. If the server is not a Galera Cluster node, then this option has no effect.

This option, when enabled and used with GTID replication, will rotate the binary logs at backup time.

mariadb-backup --backup --galera-info

`--history`

Defines whether you want to track backup history in the PERCONA_SCHEMA.xtrabackup_history table.

--history[=name]

When using this option, mariadb-backup records its operation in a table on the MariaDB Server. Passing a name to this option allows you group backups under arbitrary terms for later processing and analysis.

mariadb-backup --backup --history=backup_all

Currently, the table it uses by default is named mysql.mariadb_backup_history. Prior to MariaDB 10.11, the default table was PERCONA_SCHEMA.xtrabackup_history.

mariadb-backup will also record this in the xtrabackup_info file.

`-H, --host`

Defines the host for the MariaDB Server you want to backup.

--host=name

Using this option, you can define the host to use when connecting to a MariaDB Server over TCP/IP. By default, mariadb-backup attempts to connect to the local host.

mariadb-backup --backup \
      --host="example.com"

`--include`

This option is a regular expression to be matched against table names in databasename.tablename format. It is equivalent to the --tables option. This is only valid in innobackupex mode, which can be enabled with the --innobackupex option.

`--incremental`

Defines whether you want to take an increment backup, based on another backup. This is only valid in innobackupex mode, which can be enabled with the --innobackupex option.

mariadb-backup --innobackupex --incremental

Using this option with the --backup command option makes the operation incremental rather than a complete overwrite. When this option is specified, either the --incremental-lsn or[--incremental-basedir](mariadb-backup-options.md#-incremental-basedir) options can also be given. If neither option is given, option [--incremental-basedir](mariadb-backup-options.md#-incremental-basedir) is used by default, set to the first timestamped backup directory in the backup base directory.

mariadb-backup --innobackupex --backup --incremental \
     --incremental-basedir=/data/backups \
     --target-dir=/data/backups

If a backup is a incremental backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--incremental-basedir`

Defines whether you want to take an incremental backup, based on another backup.

--incremental-basedir=PATH

Using this option with the --backup command option makes the operation incremental rather than a complete overwrite. mariadb-backup will only copy pages from .ibd files if they are newer than the backup in the specified directory.

mariadb-backup --backup \
     --incremental-basedir=/data/backups \
     --target-dir=/data/backups

If a backup is a incremental backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--incremental-dir`

Defines whether you want to take an incremental backup, based on another backup.

--increment-dir=PATH

Using this option with --prepare command option makes the operation incremental rather than a complete overwrite. mariadb-backup will apply .delta files and log files into the target directory.

mariadb-backup --prepare \
      --increment-dir=backups/

If a backup is a incremental backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--incremental-force-scan`

Defines whether you want to force a full scan for incremental backups.

When using mariadb-backup to perform an incremental backup, this option forces it to also perform a full scan of the data pages being backed up, even when there's bitmap data on the changes. MariaDB does not support changed page bitmaps, so this option is useless in those versions. See MDEV-18985 for more information.

mariadb-backup --backup \
     --incremental-basedir=/path/to/target \
     --incremental-force-scan

`--incremental-history-name`

Defines a logical name for the backup.

--incremental-history-name=name

mariadb-backup can store data about its operations on the MariaDB Server. Using this option, you can define the logical name it uses in identifying the backup.

mariadb-backup --backup \
     --incremental-history-name=morning_backup

Currently, the table it uses by default is named mysql.mariadb_backup_history. Prior to MariaDB 10.11, the default table was PERCONA_SCHEMA.xtrabackup_history.

mariadb-backup will also record this in the xtrabackup_info file.

`--incremental-history-uuid`

Defines a UUID for the backup.

--incremental-history-uuid=name

mariadb-backup can store data about its operations on the MariaDB Server. Using this option, you can define the UUID it uses in identifying a previous backup to increment from. It checks --incremental-history-name, --incremental-basedir, and --incremental-lsn. If mariadb-backup fails to find a valid lsn, it generates an error.

mariadb-backup --backup \
      --incremental-history-uuid=main-backup012345678

Currently, the table it uses is named PERCONA_SCHEMA.xtrabackup_history, but expect that name to change in future releases. See MDEV-19246 for more information.

mariadb-backup will also record this in the xtrabackup_info file.

`--incremental-lsn`

Defines the sequence number for incremental backups.

--incremental-lsn=name

Using this option, you can define the sequence number (LSN) value for --backup operations. During backups, mariadb-backup only copies .ibd pages newer than the specified values.

WARNING: Incorrect LSN values can make the backup unusable. It is impossible to diagnose this issue.

`--innobackupex`

Deprecated

Enables innobackupex mode, which is a compatibility mode.

mariadb-backup --innobackupex

In innobackupex mode, mariadb-backup has the following differences:

To prepare a backup, the --apply-log option is used instead of the --prepare option.
To create an incremental backup, the --incremental option is supported.
The --no-timestamp option is supported.
To create a partial backup, the --include option is used instead of the --tables option.
To create a partial backup, the --databases option can still be used, but it's behavior changes slightly.
The --target-dir option is not used to specify the backup directory. The backup directory should instead be specified as a standalone argument.

The primary purpose of innobackupex mode is to allow scripts and tools to more easily migrate to mariadb-backup if they were originally designed to use the innobackupex utility that is included with Percona XtraBackup. It is not recommended to use this mode in new scripts, since it is not guaranteed to be supported forever. See MDEV-20552 for more information.

`--innodb`

This option has no effect. Set only for MySQL option compatibility.

`--innodb-adaptive-hash-index`

Enables InnoDB Adaptive Hash Index.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option you can explicitly enable the InnoDB Adaptive Hash Index. This feature is enabled by default for mariadb-backup. If you want to disable it, use --skip-innodb-adaptive-hash-index.

mariadb-backup --backup \
      --innodb-adaptive-hash-index

`--innodb-autoextend-increment`

Defines the increment in megabytes for auto-extending the size of tablespace file.

--innodb-autoextend-increment=36

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can set the increment in megabytes for automatically extending the size of tablespace data file in InnoDB.

mariadb-backup --backup \
     --innodb-autoextend-increment=35

`--innodb-buffer-pool-filename`

Using this option has no effect. It is available to provide compatibility with the MariaDB Server.

`--innodb-buffer-pool-size`

Defines the memory buffer size InnoDB uses the cache data and indexes of the table.

--innodb-buffer-pool-size=124M

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can configure the buffer pool for InnoDB operations.

mariadb-backup --backup \
      --innodb-buffer-pool-size=124M

`--innodb-checksum-algorithm`

innodb_checksum_algorithm was deprecated in MariaDB 10.5.10 and removed in MariaDB 10.6.

In earlier versions, it is used to define the checksum algorithm.

--innodb-checksum-algorithm=crc32
                           | strict_crc32
                           | innodb
                           | strict_innodb
                           | none
                           | strict_none

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can specify the algorithm mariadb-backup uses when checksumming on InnoDB tables. Currently, MariaDB supports the following algorithms CRC32, STRICT_CRC32, INNODB, STRICT_INNODB, NONE, STRICT_NONE.

mariadb-backup --backup \
      ---innodb-checksum-algorithm=strict_innodb

`--innodb-data-file-path`

Defines the path to individual data files.

--innodb-data-file-path=/path/to/file

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option you can define the path to InnoDB data files. Each path is appended to the --innodb-data-home-dir option.

mariadb-backup --backup \
     --innodb-data-file-path=ibdata1:13M:autoextend \
     --innodb-data-home-dir=/var/dbs/mysql/data

`--innodb-data-home-dir`

Defines the home directory for InnoDB data files.

--innodb-data-home-dir=PATH

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option you can define the path to the directory containing InnoDB data files. You can specific the files using the --innodb-data-file-path option.

mariadb-backup --backup \
     --innodb-data-file-path=ibdata1:13M:autoextend \
     --innodb-data-home-dir=/var/dbs/mysql/data

`--innodb-doublewrite`

Enables doublewrites for InnoDB tables.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. When using this option, mariadb-backup improves fault tolerance on InnoDB tables with a doublewrite buffer. By default, this feature is enabled. Use this option to explicitly enable it. To disable doublewrites, use the --skip-innodb-doublewrite option.

mariadb-backup --backup \
     --innodb-doublewrite

`--innodb-encrypt-log`

Defines whether you want to encrypt InnoDB logs.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can tell mariadb-backup that you want to encrypt logs from its InnoDB activity.

`--innodb-file-io-threads`

Defines the number of file I/O threads in InnoDB.

--innodb-file-io-threads=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the number of file I/O threads mariadb-backup uses on InnoDB tables.

mariadb-backup --backup \
     --innodb-file-io-threads=5

`--innodb-file-per-table`

Defines whether you want to store each InnoDB table as an .ibd file.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option causes mariadb-backup to store each InnoDB table as an .ibd file in the target directory.

`--innodb-flush-method`

Defines the data flush method. Ignored from MariaDB 11.0.

--innodb-flush-method=fdatasync 
                     | O_DSYNC 
                     | O_DIRECT 
                     | O_DIRECT_NO_FSYNC 
                     | ALL_O_DIRECT

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the data flush method mariadb-backup uses with InnoDB tables.

mariadb-backup --backup \
      --innodb-flush-method==_DIRECT_NO_FSYNC

`--innodb-io-capacity`

Defines the number of IOP's the utility can perform.

--innodb-io-capacity=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can limit the I/O activity for InnoDB background tasks. It should be set around the number of I/O operations per second that the system can handle, based on drive or drives being used.

mariadb-backup --backup \
     --innodb-io-capacity=200

`--innodb-log-checksums`

Defines whether to include checksums in the InnoDB logs.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can explicitly set mariadb-backup to include checksums in the InnoDB logs. The feature is enabled by default. To disable it, use the --skip-innodb-log-checksums option.

mariadb-backup --backup \
      --innodb-log-checksums

`--innodb-log-buffer-size`

This option has no functionality in mariadb-backup. It exists for MariaDB Server compatibility.

`--innodb-log-files-in-group`

This option has no functionality in mariadb-backup. It exists for MariaDB Server compatibility.

`--innodb-log-group-home-dir`

Defines the path to InnoDB log files.

--innodb-log-group-home-dir=PATH

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the path to InnoDB log files.

mariadb-backup --backup \
     --innodb-log-group-home-dir=/path/to/logs

`--innodb-max-dirty-pages-pct`

Defines the percentage of dirty pages allowed in the InnoDB buffer pool.

--innodb-max-dirty-pages-pct=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the maximum percentage of dirty, (that is, unwritten) pages that mariadb-backup allows in the InnoDB buffer pool.

mariadb-backup --backup \
     --innodb-max-dirty-pages-pct=80

`--innodb-open-files`

Defines the number of files kept open at a time.

--innodb-open-files=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can set the maximum number of files InnoDB keeps open at a given time during backups.

mariadb-backup --backup \
      --innodb-open-files=10

`--innodb-page-size`

Defines the universal page size.

--innodb-page-size=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the universal page size in bytes for mariadb-backup.

mariadb-backup --backup \
     --innodb-page-size=16k

`--innodb-read-io-threads`

Defines the number of background read I/O threads in InnoDB.

--innodb-read-io-threads=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can set the number of I/O threads MariaDB uses when reading from InnoDB.

mariadb-backup --backup \
      --innodb-read-io-threads=4

`--innodb-undo-directory`

Defines the directory for the undo tablespace files.

--innodb-undo-directory=PATH

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the path to the directory where you want MariaDB to store the undo tablespace on InnoDB tables. The path can be absolute.

mariadb-backup --backup \
     --innodb-undo-directory=/path/to/innodb_undo

`--innodb-undo-tablespaces`

Defines the number of undo tablespaces to use.

--innodb-undo-tablespaces=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can define the number of undo tablespaces you want to use during the backup.

mariadb-backup --backup \
      --innodb-undo-tablespaces=10

`--innodb-use-native-aio`

Defines whether you want to use native AI/O.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can enable the use of the native asynchronous I/O subsystem. It is only available on Linux operating systems.

mariadb-backup --backup \
      --innodb-use-native-aio

`--innodb-write-io-threads`

Defines the number of background write I/O threads in InnoDB.

--innodb-write-io-threads=#

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can set the number of background write I/O threads mariadb-backup uses.

mariadb-backup --backup \
     --innodb-write-io-threads=4

`--kill-long-queries-timeout`

Defines the timeout for blocking queries.

--kill-long-queries-timeout=#

When mariadb-backup runs, it issues a FLUSH TABLES WITH READ LOCK statement. It then identifies blocking queries. Using this option you can set a timeout in seconds for these blocking queries. When the time runs out, mariadb-backup kills the queries.

The default value is 0, which causes mariadb-backup to not attempt killing any queries.

mariadb-backup --backup \
      --kill-long-queries-timeout=10

`--kill-long-query-type`

Defines the query type the utility can kill to unblock the global lock.

--kill-long-query-type=ALL | UPDATE | SELECT

When mariadb-backup encounters a query that sets a global lock, it can kill the query in order to free up MariaDB Server for the backup. Using this option, you can choose the types of query it kills: SELECT, UPDATE, or both set with ALL. The default is ALL.

mariadb-backup --backup \
      --kill-long-query-type=UPDATE

`--lock-ddl-per-table`

Prevents DDL for each table to be backed up by acquiring MDL lock on that. NOTE: Unless --no-lock option was also specified, conflicting DDL queries , are killed at the end of backup This is done avoid deadlock between "FLUSH TABLE WITH READ LOCK", user's DDL query (ALTER, RENAME), and MDL lock on table.

`--log`

This option has no functionality. It is set to ensure compatibility with MySQL.

`--log-bin`

Defines the base name for the log sequence.

--log-bin[=name]

Using this option you, you can set the base name for mariadb-backup to use in log sequences.

`--log-copy-interval`

Defines the copy interval between checks done by the log copying thread.

--log-copy-interval=#

Using this option, you can define the copy interval mariadb-backup uses between checks done by the log copying thread. The given value is in milliseconds.

mariadb-backup --backup \
      --log-copy-interval=50

`--log-innodb-page-corruption`

Continue backup if InnoDB corrupted pages are found. The pages are logged in innodb_corrupted_pages and backup is finished with error. --prepare will try to fix corrupted pages. If innodb_corrupted_pages exists after --prepare in base backup directory, backup still contains corrupted pages and can not be considered as consistent.

Added in MariaDB 10.5.9

`--move-back`

Restores the backup to the data directory.

Using this command, mariadb-backup moves the backup from the target directory to the data directory, as defined by the --datadir option. You must stop the MariaDB Server before running this command. The data directory must be empty. If you want to overwrite the data directory with the backup, use the --force-non-empty-directories option.

mariadb-backup --move-back \
      --datadir=/var/mysql

Running the --move-back command moves the backup files to the data directory. Use this command if you don't want to save the backup for later. If you do want to save the backup for later, use the --copy-back command.

`--mysqld`

Used internally to prepare a backup.

`--no-backup-locks`

mariadb-backup locks the database by default when it runs. This option disables support for Percona Server's backup locks.

When backing up Percona Server, mariadb-backup would use backup locks by default. To be specific, backup locks refers to the LOCK TABLES FOR BACKUP and LOCK BINLOG FOR BACKUP statements. This option can be used to disable support for Percona Server's backup locks. This option has no effect when the server does not support Percona's backup locks.

Deprecated and has no effect from MariaDB 10.11.8, MariaDB 11.0.6, MariaDB 11.1.5 and MariaDB 11.2.4 as MariaDB will now always use backup locks for better performance. See MDEV-32932.

mariadb-backup --backup --no-backup-locks

`--no-lock`

Disables table locks with the FLUSH TABLE WITH READ LOCK statement.

Using this option causes mariadb-backup to disable table locks with the FLUSH TABLE WITH READ LOCK statement. Only use this option if:

You are not executing DML statements on non-InnoDB tables during the backup. This includes the mysql database system tables (which are MyISAM).
You are not executing any DDL statements during the backup.
You are not using the file "xtrabackup_binlog_info", which is not consistent with the data when --no-lock is used. Use the file "xtrabackup_binlog_pos_innodb" [link] instead.
All tables you're backing up use the InnoDB storage engine.

mariadb-backup --backup --no-lock

If you're considering --no-lock due to backups failing to acquire locks, this may be due to incoming replication events preventing the lock. Consider using the --safe-slave-backup option to momentarily stop the replica thread. This alternative may help the backup to succeed without resorting to --no-lock.

The --no-lock option only provides a consistent backup if the user ensures that no DDL or non-transactional table updates occur during the backup. The --no-lock option is not supported by MariaDB plc.

`--no-timestamp`

This option prevents creation of a time-stamped subdirectory of the BACKUP-ROOT-DIR given on the command line. When it is specified, the backup is done in BACKUP-ROOT-DIR instead. This is only valid in innobackupex mode, which can be enabled with the --innobackupex option.

`--no-version-check`

Disables version check.

Using this option, you can disable mariadb-backup version check.

mariadb-backup --backup --no-version-check

`--open-files-limit`

Defines the maximum number of file descriptors.

--open-files-limit=#

Using this option, you can define the maximum number of file descriptors mariadb-backup reserves with setrlimit().

mariadb-backup --backup \
      --open-files-limit=

`--parallel`

Defines the number of threads to use for parallel data file transfer.

--parallel=#

Using this option, you can set the number of threads mariadb-backup uses for parallel data file transfers. By default, it is set to 1.

`-p, --password`

Defines the password to use to connect to MariaDB Server.

--password=passwd

When you run mariadb-backup, it connects to MariaDB Server in order to access and back up the databases and tables. Using this option, you can set the password mariadb-backup uses to access the server. To set the user, use the --user option.

mariadb-backup --backup \
      --user=root \
      --password=root_password

`--plugin-dir`

Defines the directory for server plugins.

--plugin-dir=PATH

Using this option, you can define the path mariadb-backup reads for MariaDB Server plugins. It only uses it during the --prepare phase to load the encryption plugin. It defaults to the plugin_dir server system variable.

mariadb-backup --backup \
      --plugin-dir=/var/mysql/lib/plugin

`--plugin-load`

Defines the encryption plugins to load.

--plugin-load=name

Using this option, you can define the encryption plugin you want to load. It is only used during the --prepare phase to load the encryption plugin. It defaults to the server --plugin-load option.

The option was removed.

`-P, --port`

Defines the server port to connect to.

--port=#

When you run mariadb-backup, it connects to MariaDB Server in order to access and back up your databases and tables. Using this option, you can set the port the utility uses to access the server over TCP/IP. To set the host, see the --host option. Use mysql --help for more details.

mariadb-backup --backup \
      --host=192.168.11.1 \
      --port=3306

`--prepare`

Prepares an existing backup to restore to the MariaDB Server.

Files that mariadb-backup generates during --backup operations in the target directory are not ready for use on the Server. Before you can restore the data to MariaDB, you first need to prepare the backup.

In the case of full backups, the files are not point in time consistent, since they were taken at different times. If you try to restore the database without first preparing the data, InnoDB rejects the new data as corrupt. Running mariadb-backup with the --prepare command readies the data so you can restore it to MariaDB Server. When working with incremental backups, you need to use the --prepare command and the --incremental-dir option to update the base backup with the deltas from an incremental backup.

mariadb-backup --prepare

Once the backup is ready, you can use the --copy-back or the --move-back commands to restore the backup to the server.

`--print-defaults`

Prints the utility argument list, then exits.

Using this argument, MariaDB prints the argument list to stdout and then exits. You may find this useful in debugging to see how the options are set for the utility.

mariadb-backup --print-defaults

`--print-param`

Prints the MariaDB Server options needed for copyback.

Using this option, mariadb-backup prints to stdout the MariaDB Server options that the utility requires to run the --copy-back command option.

mariadb-backup --print-param

`--rollback-xa`

By default, mariadb-backup will not commit or rollback uncommitted XA transactions, and when the backup is restored, any uncommitted XA transactions must be manually committed using XA COMMIT or manually rolled back using XA ROLLBACK.

MariaDB starting with 10.5

mariadb-backup's --rollback-xa option is not present because the server has more robust ways of handling uncommitted XA transactions.

This is an experimental option. Do not use this option in older versions. Older implementation can cause corruption of InnoDB data.

`--rsync`

Defines whether to use rsync.

During normal operation, mariadb-backup transfers local non-InnoDB files using a separate call to cp for each file. Using this option, you can optimize this process by performing this transfer with rsync, instead.

mariadb-backup --backup --rsync

This option is not compatible with the --stream option.

Deprecated and has no effect from MariaDB 10.11.8, MariaDB 11.0.6, MariaDB 11.1.5 and MariaDB 11.2.4 as rsync will not work on tables that are in use. See MDEV-32932.

`--safe-slave-backup`

Stops replica SQL threads for backups.

When running mariadb-backup on a server that uses replication, you may occasionally encounter locks that block backups. Using this option, it stops replica SQL threads and waits until the Slave_open_temp_tables in the SHOW STATUS statement is zero. If there are no open temporary tables, the backup runs, otherwise the SQL thread starts and stops until there are no open temporary tables.

mariadb-backup --backup \
      --safe-slave-backup \
      --safe-slave-backup-timeout=500

The backup fails if the Slave_open_temp_tables doesn't reach zero after the timeout period set by the --safe-slave-backup-timeout option.

`--safe-slave-backup-timeout`

Defines the timeout for replica backups.

--safe-slave-backup-timeout=#

When running mariadb-backup on a server that uses replication, you may occasionally encounter locks that block backups. With the --safe-slave-backup option, it waits until the Slave_open_temp_tables in the SHOW STATUS statement reaches zero. Using this option, you set how long it waits. It defaults to 300.

mariadb-backup --backup \
      --safe-slave-backup \
      --safe-slave-backup-timeout=500

`--secure-auth`

Refuses client connections to servers using the older protocol.

Using this option, you can set it explicitly to refuse client connections to the server when using the older protocol, from before 4.1.1. This feature is enabled by default. Use the --skip-secure-auth option to disable it.

mariadb-backup --backup --secure-auth

`--skip-innodb-adaptive-hash-index`

Disables InnoDB Adaptive Hash Index.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option you can explicitly disable the InnoDB Adaptive Hash Index. This feature is enabled by default for mariadb-backup. If you want to explicitly enable it, use --innodb-adaptive-hash-index.

mariadb-backup --backup \
      --skip-innodb-adaptive-hash-index

`--skip-innodb-doublewrite`

Disables doublewrites for InnoDB tables.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. When doublewrites are enabled, InnoDB improves fault tolerance with a doublewrite buffer. By default this feature is turned on. Using this option you can disable it for mariadb-backup. To explicitly enable doublewrites, use the --innodb-doublewrite option.

mariadb-backup --backup \
     --skip-innodb-doublewrite

`--skip-innodb-log-checksums`

Defines whether to exclude checksums in the InnoDB logs.

mariadb-backup initializes its own embedded instance of InnoDB using the same configuration as defined in the configuration file. Using this option, you can set mariadb-backup to exclude checksums in the InnoDB logs. The feature is enabled by default. To explicitly enable it, use the --innodb-log-checksums option.

`--skip-secure-auth`

Refuses client connections to servers using the older protocol.

Using this option, you can set it accept client connections to the server when using the older protocol, from before 4.1.1. By default, it refuses these connections. Use the --secure-auth option to explicitly enable it.

mariadb-backup --backup --skip-secure-auth

`--slave-info`

Prints the binary log position and the name of the primary server.

If the server is a replica, then this option causes mariadb-backup to print the hostname of the replica's replication primary and the binary log file and position of the replica's SQL thread to stdout.

This option also causes mariadb-backup to record this information as a CHANGE MASTER command that can be used to set up a new server as a replica of the original server's primary after the backup has been restored. This information are written to the xtrabackup_slave_info file.

mariadb-backup does not check if GTIDs are being used in replication. It takes a shortcut and assumes that if the gtid_slave_pos system variable is non-empty, then it writes the CHANGE MASTER command with the MASTER_USE_GTID option set to slave_pos. Otherwise, it writes the CHANGE MASTER command with the MASTER_LOG_FILE and MASTER_LOG_POS options using the primary's binary log file and position. See MDEV-19264 for more information.

mariadb-backup --slave-info

`-S, --socket`

Defines the socket for connecting to local database.

--socket=name

Using this option, you can define the UNIX domain socket you want to use when connecting to a local database server. The option accepts a string argument. For more information, see the mysql --help command.

mariadb-backup --backup \
      --socket=/var/mysql/mysql.sock

`--ssl`

Enables TLS. By using this option, you can explicitly configure mariadb-backup to encrypt its connection with TLS when communicating with the server. You may find this useful when performing backups in environments where security is extra important or when operating over an insecure network.

TLS is also enabled even without setting this option when certain other TLS options are set. For example, see the descriptions of the following options:

--ssl-ca
--ssl-capath
--ssl-cert
--ssl-cipher
--ssl-key

`--ssl-ca`

Defines a path to a PEM file that should contain one or more X509 certificates for trusted Certificate Authorities (CAs) to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-ca=/etc/my.cnf.d/certificates/ca.pem

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem

See Secure Connections Overview: Certificate Authorities (CAs) for more information.

This option implies the --ssl option.

`--ssl-capath`

Defines a path to a directory that contains one or more PEM files that should each contain one X509 certificate for a trusted Certificate Authority (CA) to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-capath=/etc/my.cnf.d/certificates/ca/

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem \
   --ssl-capath=/etc/my.cnf.d/certificates/ca/

The directory specified by this option needs to be run through the openssl rehash command.

See Secure Connections Overview: Certificate Authorities (CAs) for more information

This option implies the --ssl option.

`--ssl-cert`

Defines a path to the X509 certificate file to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem

This option implies the --ssl option.

`--ssl-cipher`

Defines the list of permitted ciphers or cipher suites to use for TLS. For example:

--ssl-cipher=name

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem
   --ssl-cipher=TLSv1.2

To determine if the server restricts clients to specific ciphers, check the ssl_cipher system variable.

This option implies the --ssl option.

`--ssl-crl`

Defines a path to a PEM file that should contain one or more revoked X509 certificates to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-crl=/etc/my.cnf.d/certificates/crl.pem

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem \
   --ssl-crl=/etc/my.cnf.d/certificates/crl.pem

See Secure Connections Overview: Certificate Revocation Lists (CRLs) for more information.

This option is only supported if mariadb-backup was built with OpenSSL. If mariadb-backup was built with yaSSL, then this option is not supported. See TLS and Cryptography Libraries Used by MariaDB for more information about which libraries are used on which platforms.

`--ssl-crlpath`

Defines a path to a directory that contains one or more PEM files that should each contain one revoked X509 certificate to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-crlpath=/etc/my.cnf.d/certificates/crl/

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem \
   --ssl-crlpath=/etc/my.cnf.d/certificates/crl/

The directory specified by this option needs to be run through the openssl rehash command.

See Secure Connections Overview: Certificate Revocation Lists (CRLs) for more information.

`--ssl-key`

Defines a path to a private key file to use for TLS. This option requires that you use the absolute path, not a relative path. For example:

--ssl-key=/etc/my.cnf.d/certificates/client-key.pem

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem

This option implies the --ssl option.

`--ssl-verify-server-cert`

Enables server certificate verification. This option is disabled by default.

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem \
   --ssl-verify-server-cert

`--stream`

Streams backup files to stdout.

--stream=xbstream

Using this command option, you can set mariadb-backup to stream the backup files to stdout in the given format. Currently, the supported format is xbstream.

mariadb-backup --stream=xbstream > backup.xb

To extract all files from the xbstream archive into a directory use the mbstream utility

mbstream  -x < backup.xb

If a backup is streamed, then mariadb-backup will record the format in the xtrabackup_info file.

`--tables`

Defines the tables you want to include in the backup.

--tables=REGEX

Using this option, you can define what tables you want mariadb-backup to back up from the database. The table values are defined using Regular Expressions. To define the tables you want to exclude from the backup, see the --tables-exclude option.

mariadb-backup --backup \
     --databases=example
     --tables=nodes_* \
     --tables-exclude=nodes_tmp

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--tables-exclude`

Defines the tables you want to exclude from the backup.

--tables-exclude=REGEX

Using this option, you can define what tables you want mariadb-backup to exclude from the backup. The table values are defined using Regular Expressions. To define the tables you want to include from the backup, see the --tables option.

mariadb-backup --backup \
     --databases=example
     --tables=nodes_* \
     --tables-exclude=nodes_tmp

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--tables-file`

Defines path to file with tables for backups.

--tables-file=/path/to/file

Using this option, you can set a path to a file listing the tables you want to back up. mariadb-backup iterates over each line in the file. The format is database.table.

mariadb-backup --backup \
     --databases=example \
     --tables-file=/etc/mysql/backup-file

If a backup is a partial backup, then mariadb-backup will record that detail in the xtrabackup_info file.

`--target-dir`

Defines the destination directory.

--target-dir=/path/to/target

Using this option you can define the destination directory for the backup. mariadb-backup writes all backup files to this directory. mariadb-backup will create the directory, if it does not exist (but it will not create the full path recursively, i.e. at least parent directory if the --target-dir must exist=

mariadb-backup --backup \
       --target-dir=/data/backups

`--throttle`

Defines the limit for I/O operations per second in IOS values.

--throttle=#

Using this option, you can set a limit on the I/O operations mariadb-backup performs per second in IOS values. It is only used during the --backup command option.

`--tls-version`

This option accepts a comma-separated list of TLS protocol versions. A TLS protocol version will only be enabled if it is present in this list. All other TLS protocol versions will not be permitted. For example:

--tls-version="TLSv1.2,TLSv1.3"

This option is usually used with other TLS options. For example:

mariadb-backup --backup \
   --ssl-cert=/etc/my.cnf.d/certificates/client-cert.pem \
   --ssl-key=/etc/my.cnf.d/certificates/client-key.pem \
   --ssl-ca=/etc/my.cnf.d/certificates/ca.pem \
   --tls-version="TLSv1.2,TLSv1.3"

See Secure Connections Overview: TLS Protocol Versions for more information.

`-t, --tmpdir`

Defines path for temporary files.

--tmpdir=/path/tmp[;/path/tmp...]

Using this option, you can define the path to a directory mariadb-backup uses in writing temporary files. If you want to use more than one, separate the values by a semicolon (that is, ;). When passing multiple temporary directories, it cycles through them using round-robin.

mariadb-backup --backup \
     --tmpdir=/data/tmp;/tmp

`--use-memory`

Defines the buffer pool size that is used during the prepare stage.

--use-memory=124M

Using this option, you can define the buffer pool size for mariadb-backup. Use it instead of buffer_pool_size.

mariadb-backup --prepare \
      --use-memory=124M

`--user`

Defines the username for connecting to the MariaDB Server.

--user=name
-u name

When mariadb-backup runs, it connects to the specified MariaDB Server to get its backups. Using this option, you can define the database user used for authentication. Starting from MariaDB 10.5.24, MariaDB 10.6.17, MariaDB 10.11.7, MariaDB 11.0.5, MariaDB 11.1.4, MariaDB 11.2.3, MariaDB 11.3.2, MariaDB 11.4.1, if the --user option is ommited, the user name is detected from the OS.

mariadb-backup --backup \
      --user=root \
      --password=root_passwd

`--verbose`

Displays verbose output

mariadb-backup --verbose

`--version`

Prints version information.

Using this option, you can print the mariadb-backup version information to stdout.

mariadb-backup --version

_{This page is licensed: CC BY-SA / Gnu FDL}

Previousmariadb-backup Overview NextFull Backup and Restore with mariadb-backup

Last updated 2 months ago

Was this helpful?

List of mariadb-backup Options

--apply-log

--apply-log-only

--backup

--binlog-info

--close-files

--compress

--compress-chunk-size

--compress-threads

--copy-back

--core-file

--databases

--databases-exclude

--databases-file

-h, --datadir

--debug-sleep-before-unlock

--decompress

--debug-sync

--defaults-extra-file

--defaults-file

--defaults-group

--encrypted-backup

--export

--extra-lsndir

--force-non-empty-directories

--ftwrl-wait-query-type

--ftwrl-wait-threshold

--ftwrl-wait-timeout

--galera-info

--history

-H, --host

--include

--incremental

--incremental-basedir

--incremental-dir

--incremental-force-scan

--incremental-history-name

--incremental-history-uuid

--incremental-lsn

--innobackupex

--innodb

--innodb-adaptive-hash-index

--innodb-autoextend-increment

--innodb-buffer-pool-filename

--innodb-buffer-pool-size

--innodb-checksum-algorithm

--innodb-data-file-path

--innodb-data-home-dir

--innodb-doublewrite

--innodb-encrypt-log

--innodb-file-io-threads

--innodb-file-per-table

--innodb-flush-method

--innodb-io-capacity

--innodb-log-checksums

--innodb-log-buffer-size

--innodb-log-files-in-group

--innodb-log-group-home-dir

--innodb-max-dirty-pages-pct

--innodb-open-files

--innodb-page-size

--innodb-read-io-threads

--innodb-undo-directory

--innodb-undo-tablespaces

--innodb-use-native-aio

--innodb-write-io-threads

--kill-long-queries-timeout

--kill-long-query-type

--lock-ddl-per-table

--log

--log-bin

--log-copy-interval

--log-innodb-page-corruption

--move-back

--mysqld

--no-backup-locks

--no-lock

--no-timestamp

--no-version-check

--open-files-limit

List of `mariadb-backup` Options

`--apply-log`

`--apply-log-only`

`--backup`

`--binlog-info`

`--close-files`

`--compress`

`--compress-chunk-size`

`--compress-threads`

`--copy-back`

`--core-file`

`--databases`

`--databases-exclude`

`--databases-file`

`-h, --datadir`

`--debug-sleep-before-unlock`

`--decompress`

`--debug-sync`

`--defaults-extra-file`

`--defaults-file`

`--defaults-group`

`--encrypted-backup`

`--export`

`--extra-lsndir`

`--force-non-empty-directories`

`--ftwrl-wait-query-type`

`--ftwrl-wait-threshold`

`--ftwrl-wait-timeout`

`--galera-info`

`--history`

`-H, --host`

`--include`

`--incremental`

`--incremental-basedir`

`--incremental-dir`

`--incremental-force-scan`

`--incremental-history-name`

`--incremental-history-uuid`

`--incremental-lsn`

`--innobackupex`

`--innodb`

`--innodb-adaptive-hash-index`

`--innodb-autoextend-increment`

`--innodb-buffer-pool-filename`

`--innodb-buffer-pool-size`

`--innodb-checksum-algorithm`

`--innodb-data-file-path`

`--innodb-data-home-dir`

`--innodb-doublewrite`

`--innodb-encrypt-log`

`--innodb-file-io-threads`

`--innodb-file-per-table`

`--innodb-flush-method`

`--innodb-io-capacity`

`--innodb-log-checksums`

`--innodb-log-buffer-size`

`--innodb-log-files-in-group`

`--innodb-log-group-home-dir`

`--innodb-max-dirty-pages-pct`

`--innodb-open-files`

`--innodb-page-size`

`--innodb-read-io-threads`

`--innodb-undo-directory`

`--innodb-undo-tablespaces`

`--innodb-use-native-aio`

`--innodb-write-io-threads`

`--kill-long-queries-timeout`

`--kill-long-query-type`

`--lock-ddl-per-table`

`--log`

`--log-bin`

`--log-copy-interval`

`--log-innodb-page-corruption`

`--move-back`

`--mysqld`

`--no-backup-locks`

`--no-lock`

`--no-timestamp`

`--no-version-check`

`--open-files-limit`