shell> mariadb-dump [options] db_name [tbl_name ...]
shell> mariadb-dump [options] --databases db_name ...
shell> mariadb-dump [options] --all-databases
shell> mariadb-dump [options] --system={options}

Display a help message and exit.

Add a DROP DATABASE statement before each CREATE DATABASE statement. This option is typically used in conjunction with the --all-databases or --databases option because no CREATE DATABASE statements are written unless one of those options is specified.

Add a DROP TABLE statement before each CREATE TABLE statement.

Add a DROP TRIGGER statement before each CREATE TRIGGER statement.

Surround each table dump with LOCK TABLES and UNLOCK TABLES statements. This results in faster inserts when the dump file is reloaded.

Dump all tables in all databases. This is the same as using the --databases option and naming all the databases on the command line.

Adds to a table dump all SQL statements needed to create any tablespaces used by an NDBCLUSTER table. This information is not otherwise included in the output from mariadb-dump. This option is currently relevant only to MySQL Cluster tables.

Allow creation of column names that are keywords. This works by prefixing each column name with the table name.

Adds 'STOP SLAVE' prior to 'CHANGE MASTER' and 'START SLAVE' to bottom of dump.

Dump system versioned table as of specified timestamp.

The directory where character sets are installed.

Write additional information in the dump file such as program version, server version, and host. This option is enabled by default. To suppress this additional information, use --skip-comments.

Produce more compact output. This option enables the --skip-add-drop-table, --skip-add-locks, --skip-comments, --skip-disable-keys, and --skip-set-charset options.

Produce output that is more compatible with other database systems or with older MySQL servers. The value of name can be ansi, mysql323, mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options, no_table_options, or no_field_options. To use several values, separate them by commas. These values have the same meaning as the corresponding options for setting the server SQL mode.

This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible. For example, --compatible=oracle does not map data types to Oracle types or use Oracle comment syntax.

Use complete INSERT statements that include column names.

Compress all information sent between the client and the server if both support compression.

By default S3 tables are ignored. With this option set, the result file will contain a CREATE statement for a similar Aria table, followed by the table data and ending with an ALTER TABLE xxx ENGINE=S3.

Include all MariaDB-specific table options in the CREATE TABLE statements. Use --skip-create-options to disable.

Dump several databases. Normally, mariadb-dump treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names. CREATE DATABASE and USE statements are included in the output before each new database.

Write a debugging log. A typical debug_options string is 'd:t:o,file_name'. The default value is 'd:t:o,/tmp/mariadb-dump.trace'.

Print some debugging information when the program exits.

Print debugging information and memory and CPU usage statistics when the program exits.

Default authentication client-side plugin to use.

Use charset_name as the default character set. If no character set is specified, mariadb-dump uses utf8.

Set filename as the file to read default options from after the global defaults files has been read. Must be given as first option.

Set filename as the file to read default options from, override global defaults files. Must be given as first option.

Also read groups with a suffix of str. For example, since mariadb-dump normally reads the [client] and [mariadb-dump] groups, --defaults-group-suffix=x would cause it to also read the groups [mariadb-dump_x] and [client_x].

Write INSERT DELAYED statements rather than INSERT statements.

On a master replication server, delete the binary logs by sending a PURGE BINARY LOGS statement to the server after performing the dump operation. This option automatically enables --master-data.

For each table, surround the INSERT statements with /*!40000 ALTER TABLE tbl_name DISABLE KEYS */; and /*!40000 ALTER TABLE tbl_name ENABLE KEYS */; statements. This makes loading the dump file faster because the indexes are created after all rows are inserted. This option is effective only for nonunique indexes of MyISAM tables.

If the --comments option is given, mariadb-dump produces a comment at the end of the dump of the following form:

-- Dump completed on DATE

However, the date causes dump files taken at different times to appear to be different, even if the data are otherwise identical. --dump-date and --skip-dump-date control whether the date is added to the comment. The default is --dump-date (include the date in the comment). --skip-dump-date suppresses date printing

Dump tables with history. Until this option, mariadb-dump could not read historical rows from versioned tables, and so historical data would not be backed up.

Used for producing a dump file from a replication slave server that can be used to set up another slave server with the same master. Causes the binary log position and filename of the master to be appended to the dumped data output. Setting the value to 1 (the default) will print it as a CHANGE MASTER command in the dumped data output; if set to 2, that command will be prefixed with a comment symbol. This option will turn --lock-all-tables on, unless --single-transaction is specified too (in which case a global read lock is only taken a short time at the beginning of the dump - don't forget to read about --single-transaction below). In all cases any action on logs will happen at the exact moment of the dump. Option automatically turns --lock-tables off. Using this option causes mariadb-dump to stop the slave SQL thread before beginning the dump, and restart it again after completion.

Include Event Scheduler events for the dumped databases in the output.

Use multiple-row INSERT syntax that include several VALUES lists. This results in a smaller dump file and speeds up inserts when the file is reloaded.

These options are used with the --tab option and have the same meaning as the corresponding FIELDS clauses for LOAD DATA INFILE.

Removed in MariaDB 5.5. Use --lock-all-tables instead.

Flush the MariaDB server log files before starting the dump. This option requires the RELOAD privilege. If you use this option in combination with the --all-databases option, the logs are flushed for each database dumped. The exception is when using --lock-all-tables or --master-data: In this case, the logs are flushed only once, corresponding to the moment that all tables are locked. If you want your dump and the log flush to happen at exactly the same moment, you should use --flush-logs together with either --lock-all-tables or --master-data.

Send a FLUSH PRIVILEGES statement to the server after dumping the mysql database. This option should be used any time the dump contains the mysql database and any other database that depends on the data in the mysql database for proper restoration.

Continue even if an SQL error occurs during a table dump.

One use for this option is to cause mariadb-dump to continue executing even when it encounters a view that has become invalid because the definition refers to a table that has been dropped. Without --force, mariadb-dump exits with an error message. With --force, mariadb-dump prints the error message, but it also writes an SQL comment containing the view definition to the dump output and continues executing.

Available from MariaDB 10.0.13, and is used together with --master-data and --dump-slave to more conveniently set up a new GTID slave. It causes those options to output SQL statements that configure the slave to use the global transaction ID to connect to the master instead of old-style filename/offset positions. The old-style positions are still included in comments when --gtid is used; likewise the GTID position is included in comments even if --gtid is not used.

Used together with --tab. When enabled, adds header with column names to the top of output txt files.

Dump binary columns using hexadecimal notation (for example, 'abc' becomes 0x616263). The affected data types are BINARY, VARBINARY, the BLOB types, and BIT.

Dump data from the MariaDB server on the given host. The default host is localhost.

Do not dump the given table, which must be specified using both the database and table names. To ignore multiple tables, use this option multiple times. This option also can be used to ignore views.

Add the MASTER_HOST and MASTER_PORT options for the CHANGE MASTER TO statement when using the --dump-slave option for a slave dump.

Write INSERT IGNORE statements rather than INSERT statements.

This option is used with the --tab option and has the same meaning as the corresponding LINES clause for LOAD DATA INFILE.

Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump. This option automatically turns off --single-transaction and --lock-tables.

For each dumped database, lock all tables to be dumped before dumping them. The tables are locked with READ LOCAL to allow concurrent inserts in the case of MyISAM tables. For transactional tables such as InnoDB, --single-transaction is a much better option than --lock-tables because it does not need to lock the tables at all.

Because --lock-tables locks tables for each database separately, this option does not guarantee that the tables in the dump file are logically consistent between databases. Tables in different databases may be dumped in completely different states.

Use --skip-lock-tables to disable.

Log warnings and errors by appending them to the named file. The default is to do no logging.

When restoring the dump, the server will, if logging is turned on, log the queries to the general and slow query log. Defaults to on; use --skip-log-queries to disable.

Use this option to dump a master replication server to produce a dump file that can be used to set up another server as a slave of the master. It causes the dump output to include a CHANGE MASTER TO statement that indicates the binary log coordinates (file name and position) of the dumped server. These are the master server coordinates from which the slave should start replicating after you load the dump file into the slave.

If the option value is 2, the CHANGE MASTER TO statement is written as an SQL comment, and thus is informative only; it has no effect when the dump file is reloaded. If the option value is 1, the statement is not written as a comment and takes effect when the dump file is reloaded. If no option value is specified, the default value is 1.

This option requires the RELOAD privilege and the binary log must be enabled.

The --master-data option automatically turns off --lock-tables. It also turns on --lock-all-tables, unless --single-transaction also is specified. In all cases, any action on logs happens at the exact moment of the dump.

It is also possible to set up a slave by dumping an existing slave of the master. To do this, use the following procedure on the existing slave:

mariadb> STOP SLAVE SQL_THREAD;
mariadb> SHOW SLAVE STATUS;

shell> mariadb-dump --master-data=2 --all-databases > dumpfile

mariadb> START SLAVE;

shell> mariadb < dumpfile

mariadb> CHANGE MASTER TO
    -> MASTER_LOG_FILE = 'file_name', MASTER_LOG_POS = file_pos;

Sets the maximum packet length to send to or receive from server.

Sets the maximum time any statement can run before being timed out by the server. (Default value is 0 (no limit))

Sets the buffer size for TCP/IP and socket communication.

Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements.

This option suppresses the CREATE DATABASE statements that are otherwise included in the output if the --databases or --all-databases option is given.

Do not write CREATE TABLE statements that re-create each dumped table.

Do not write any table row information (that is, do not dump table contents). This is useful if you want to dump only the CREATE TABLE statement for the table (for example, to create an empty copy of the table by loading the dump file).

Do not read default options from any option file. This must be given as the first argument.

This has the same effect as --skip-set-charset.

This option is shorthand. It is the same as specifying --add-drop-table --add-locks --create-options --disable-keys --extended-insert --lock-tables --quick --set-charset. It should give you a fast dump operation and produce a dump file that can be reloaded into a MariaDB server quickly.

The --opt option is enabled by default. Use --skip-opt to disable it. See the discussion at the beginning of this section for information about selectively enabling or disabling a subset of the options affected by --opt.

Dump each table's rows sorted by its primary key, or by its first unique index, if such an index exists. This is useful when dumping a MyISAM table to be loaded into an InnoDB table, but will make the dump operation take considerably longer.

Dump each table according to their size, smallest first. Useful when using --single-transaction on tables which get truncated/altered often. The assumption here is that smaller tables get truncated more often, and by dumping those first, this reduces the chance that a --single-transaction dump will fail with with

Number of dump table jobs executed in parallel (only for use with the --tab option). Initial testing indicates that performance can be increased (dump time decreased) up to 4 times on smaller size dumps, when the database fits into memory. There is a point at which disk becomes the bottleneck, after which adding more parallel jobs does not bring better performance.

The password to use when connecting to the server. If you use the short option form (-p), you cannot have a space between the option and the password. If you omit the password value following the --password or -p option on the command line, mariadb-dump prompts for one.

Specifying a password on the command line should be considered insecure. You can use an option file to avoid giving the password on the command line.

On Windows, connect to the server via a named pipe. This option applies only if the server supports named-pipe connections.

Directory for client-side plugins.

The TCP/IP port number to use for the connection. Forces --protocol=tcp when specified on the command line without other connection properties.

The connection protocol to use for connecting to the server. It is useful when the other connection parameters normally would cause a protocol to be used other than the one you want.

This option is useful for dumping large tables. It forces mariadb-dump to retrieve rows for a table from the server a row at a time rather than retrieving the entire row set and buffering it in memory before writing it out.

Print the program argument list and exit. This must be given as the first argument.

Quote identifiers (such as database, table, and column names) within “`” characters. If the ANSI_QUOTES SQL mode is enabled, identifiers are quoted within “"” characters. This option is enabled by default. It can be disabled with --skip-quote-names, but this option should be given after any option such as --compatible that may enable --quote-names.

Write REPLACE statements rather than INSERT statements.

Direct output to a given file. This option should be used on Windows to prevent newline “\n” characters from being converted to “\r\n” carriage return/newline sequences. The result file is created and its previous contents overwritten, even if an error occurs while generating the dump.

Included stored routines (procedures and functions) for the dumped databases in the output. Use of this option requires the SELECT privilege for the mysql.proc table. The output generated by using --routines contains CREATE PROCEDURE and CREATE FUNCTION statements to re-create the routines. However, these statements do not include attributes such as the routine creation and modification timestamps. This means that when the routines are reloaded, they will be created with the timestamps equal to the reload time.

If you require routines to be re-created with their original timestamp attributes, do not use --routines. Instead, dump and reload the contents of the mysql.proc table directly, using a MariaDB account that has appropriate privileges for the mysql database.

Add SET NAMES default_character_set to the output. This option is enabled by default. To suppress the SET NAMES statement, use --skip-set-charset.

This option sends a START TRANSACTION SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state of the database at the time when BEGIN was issued without blocking any applications.

When using this option, you should keep in mind that only InnoDB tables are dumped in a consistent state. For example, any MyISAM or MEMORY tables dumped while using this option may still change state.

While a --single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements: ALTER TABLE, CREATE TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE. A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the SELECT that is performed by mariadb-dump to retrieve the table contents to obtain incorrect contents or fail.

The --single-transaction option and the --lock-tables option are mutually exclusive because LOCK TABLES causes any pending transactions to be committed implicitly.

To dump large tables, you should combine the --single-transaction option with --quick.

Disable the --add-drop-table option.

Disable the --add-locks option.

Disable the --comments option.

Disable the --compact option.

Disable the --disable-keys option.

Disable the --extended-insert option.

Disable the --opt option.

Disable the --quick option.

Disable the --quote-names option.

Disable the --set-charset option.

Disable the --triggers option.

Disable the --tz-utc option.

For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use. Forces --protocol=socket when specified on the command line without other connection properties; on Windows, forces --protocol=pipe.

Enable SSL for connection (automatically enabled with other flags). Disable with --skip-ssl.

CA file in PEM format (check OpenSSL docs, implies --ssl).

CA directory (check OpenSSL docs, implies --ssl).

X509 cert in PEM format (check OpenSSL docs, implies --ssl).

SSL cipher to use (check OpenSSL docs, implies --ssl).

X509 key in PEM format (check OpenSSL docs, implies --ssl).

Certificate revocation list (check OpenSSL docs, implies --ssl).

Certificate revocation list path (check OpenSSL docs, implies --ssl).

Verify server's "Common Name" in its cert against hostname used when connecting. This option is disabled by default.

Dump the system tables in the mysql database in a logical form. This option is an empty set by default.

One or more options can be listed in comma separated list.

The options here are:

The format of the output is affected by --replace and --insert-ignore. The --replace option will output CREATE OR REPLACE forms of SQL, and also DROP IF EXISTS prior to CREATE, if a CREATE OR REPLACE option isn't available.

With --system=user (or all), and --replace, SQL is generated to generate an error if attempting to import the dump with a connection user that is being replaced within the dump.

The --insert-ignore option will cause CREATE IF NOT EXIST forms of SQL to generated if available.

For stats, and timezones, --replace and --insert-ignore have the usual effects.

Enabling specific options here will cause the relevant tables in the mysql database to be ignored when dumping the mysql database or --all-databases.

To help in migrating from MySQL to MariaDB, this option is designed to be able to dump system information from MySQL-5.7 and 8.0 servers. SQL generated is also experimentally compatible with MySQL-5.7/8.0. Mappings of implementation specific grants/plugins isn't always one-to-one however between MariaDB and MySQL and will require manual changes.

Produce tab-separated text-format data files. For each dumped table, mariadb-dump creates a tbl_name.sql file that contains the CREATE TABLE statement that creates the table, and the server writes a tbl_name.txt file that contains its data. The option value is the directory in which to write the files.

Column values are converted to the character set specified by the --default-character-set option.

Override the --databases or -B option. mariadb-dump regards all name arguments following the option as table names.

Include triggers for each dumped table in the output. This option is enabled by default; disable it with --skip-triggers.

This option enables TIMESTAMP columns to be dumped and reloaded between servers in different time zones. mariadb-dump sets its connection time zone to UTC and adds SET TIME_ZONE='+00:00' to the dump file. Without this option, TIMESTAMP columns are dumped and reloaded in the time zones local to the source and destination servers, which can cause the values to change if the servers are in different time zones. --tz-utc also protects against changes due to daylight saving time. --tz-utc is enabled by default. To disable it, use --skip-tz-utc.

The MariaDB user name to use when connecting to the server.

Verbose mode. Print more information about what the program does.

Display version information and exit.

Dump only rows selected by the given WHERE condition. Quotes around the condition are mandatory if it contains spaces or other characters that are special to your command interpreter.

Examples:

--where="user='jimf'"
-w"userid>1"
-w"userid<1"

Write dump output as well-formed XML.

NULL, 'NULL', and Empty Values: For a column named column_name, the NULL value, an empty string, and the string value 'NULL' are distinguished from one another in the output generated by this option as follows.

The output from the mariadb client when run using the --xml option also follows the preceding rules. (See the section called “MARIADB OPTIONS”.)

XML output from mariadb-dump includes the XML namespace, as shown here:

shell> mariadb-dump --xml -u root world City
<?xml version="1.0"?>
<mariadb-dump xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<database name="world">
<table_structure name="City">
<field Field="ID" Type="int(11)" Null="NO" Key="PRI" Extra="auto_increment" />
<field Field="Name" Type="char(35)" Null="NO" Key="" Default="" Extra="" />
<field Field="CountryCode" Type="char(3)" Null="NO" Key="" Default="" Extra="" />
<field Field="District" Type="char(20)" Null="NO" Key="" Default="" Extra="" />
<field Field="Population" Type="int(11)" Null="NO" Key="" Default="0" Extra="" />
<key Table="City" Non_unique="0" Key_name="PRIMARY" Seq_in_index="1" Column_name="ID"
Collation="A" Cardinality="4079" Null="" Index_type="BTREE" Comment="" />
<options Name="City" Engine="MyISAM" Version="10" Row_format="Fixed" Rows="4079"
Avg_row_length="67" Data_length="273293" Max_data_length="18858823439613951"
Index_length="43008" Data_free="0" Auto_increment="4080"
Create_time="2007-03-31 01:47:01" Update_time="2007-03-31 01:47:02"
Collation="latin1_swedish_ci" Create_options="" Comment="" />
</table_structure>
<table_data name="City">
<row>
<field name="ID">1</field>
<field name="Name">Kabul</field>
<field name="CountryCode">AFG</field>
<field name="District">Kabol</field>
<field name="Population">1780000</field>
</row>
...
<row>
<field name="ID">4079</field>
<field name="Name">Rafah</field>
<field name="CountryCode">PSE</field>
<field name="District">Rafah</field>
<field name="Population">92020</field>
</row>
</table_data>
</database>
</mariadb-dump>

The maximum size of the buffer for client/server communication. The maximum is 1GB.

A query that has taken more than max_statement_time seconds will be aborted and the backup will fail. The argument will be treated as a decimal value with microsecond precision. A value of 0 (default) means no timeout. The maximum timeout is 31536000 seconds.

The initial size of the buffer for client/server communication. When creating multiple-row INSERT statements (as with the --extended-insert or --opt option), mariadb-dump creates rows up to net_buffer_length length. If you increase this variable, you should also ensure that the net_buffer_length variable in the MariaDB server is at least this large.

shell> mariadb-dump db_name > backup-file.sql

shell> mariadb db_name < backup-file.sql

shell> mariadb -e "source /path-to-backup/backup-file.sql" db_name

shell> mariadb-dump --opt db_name | mariadb --host=remote_host -C db_name

shell> mariadb-dump --databases db_name1 [db_name2 ...] > my_databases.sql

shell> mariadb-dump --all-databases > all_databases.sql

shell> mariadb-dump --all-databases --single-transaction > all_databases.sql

shell> mariadb-dump --all-databases --master-data=2 > all_databases.sql

shell> mariadb-dump --all-databases --flush-logs --master-data=2
              > all_databases.sql