Explore backup, restore, and import clients for MariaDB Server. This section details various utilities that facilitate data protection, recovery, and seamless data loading into your databases.
The mariadb-dump client is a backup program originally written by Igor Romanenko.
mariadb-dump generates a command at the beginning of the dump to enable sandbox mode. This command cannot be interpreted by earlier versions of the mariadb command-line client or by the MySQL command-line client mysql – an error is thrown if used against client versions that do not support it. This does not affect other methods of importing the data.
mariadb-dump is used to dump a database or a collection of databases for backup, or transferring data to another database server (not necessarily MariaDB or MySQL). The dump contains SQL statements to create databases, tables, table data, and more. It can also be used to generate files in CSV, XML, or other formats that use delimiters.
mariadb-dump dumps triggers along with tables, as these are part of the table definition. However, , , and are not dumped, and need extra parameters to be recreated explicitly (for example, --routines and --events). and are also part of the system tables (for example, ).
mariadb-dump supports the .
mariadb-dump doesn't consume much CPU – by default, it uses a single thread. This method is good for a heavily loaded server.
Disk input/output per second (IOPS) can, however, increase for multiple reasons. When backing up on the same device as the database, this produces unnecessary random IOPS. The dump is done sequentially, on a per-table basis, causing a full table scan and many buffer page misses on tables that are not fully cached in memory.
It's recommended that you back up from a network location to remove disk IOPS on the database server, but it is vital to use a separate network card to keep network bandwidth available for regular traffic.
Although mariadb-dump by default preserves your resources for regular spindle disks and low-core hardware, this doesn't mean that concurrent dumps cannot benefit from hardware architecture like SAN, flash storage, low write workload. The backup time would benefit from a tool such as MyDumper.
There are four general ways to invoke mariadb-dump:
If you do not name any tables after specifying db_name , or if you use the --databases or --all-databases option, entire databases are dumped.
mariadb-dump does not dump the INFORMATION_SCHEMA (or PERFORMANCE_SCHEMA, if enabled) database by default. MariaDB dumps the INFORMATION_SCHEMA if you name it explicitly on the command line, although you must also use the --skip-lock-tables option.
To see a list of the options your version of mariadb-dump supports, execute mariadb-dump --help.
mariadb-dump can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the --quick option (or --opt, which enables --quick). The --opt option (and hence --quick) is enabled by default, so to enable memory buffering, use --skip-quick.
mariadb-dump includes logic to cater for the .
If you are using a recent version of mariadb-dump to generate a dump to be reloaded into a very old MySQL server, you should not use the --opt or --extended-insert option. Use --skip-opt instead.
mariadb-dump supports the following options:
Deprecated. Use --create-options instead.
Dump all the databases. This is the same as --databases with all databases selected.
Dump all the tablespaces.
Do not dump any tablespace information.
Add a before each create. Typically used in conjunction with the --all-databases or --databases option, because no statements are written, unless one of those options is specified.
Add a before each create.
Add a statement before each .
Add locks around statements, which results in faster inserts when the dump file is reloaded. Use --skip-add-locks to disable.
Allow creation of column names that are keywords. This works by prefixing each column name with the table name.
Adds prior to and to bottom of dump.
Dump as of specified timestamp. Argument is interpreted according to the --tz-utc setting. Table structures are always dumped as of current timestamp. This option is available from MariaDB 10.7.
Directory for files.
Write additional information in the dump file such as program version, server version, and host. Disable with --skip-comments.
Give less verbose output (useful for debugging). Disables structure comments and header/footer constructs. Enables the --skip-add-drop-table, --skip-add-locks, --skip-comments, --skip-disable-keys, and --skip-set-charset options.
Change the dump to be compatible with a given mode. By default tables are dumped in a format optimized for MariaDB and MySQL. Legal modes are: ansi, mysql323, mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options, no_table_options, and no_field_options. You can use several modes, separated by commas. This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are 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 statements that include column names.
Use compression in server/client protocol. Both client and server must support compression for this to work.
By default, tables are ignored. With this option set, the result file will contain a CREATE statement for a similar table, followed by the table data and ending with an ALTER TABLE`` ``table`` ``ENGINE=S3.
Include all MariaDB and/or MySQL specific create options in 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. and statements are included in the output before each new database.
If using a debug version of MariaDB, write a debugging log. A typical debug_options string is d:t:o,file_name. The default value is d:t:o,/tmp/mysqldump.trace. If using a non-debug version, mariadb-dump will catch this and exit.
Check memory and open file usage at exit.
Print some debug info at exit.
Default authentication client-side plugin to use.
Set the default to name. If no character set is specified, mariadb-dump uses utf8mb4.
Read the file name after the global files are read. Must be given as the first argument.
Only read default options from the given file name. Must be given as the first argument.
Also read groups with a suffix of str. For example, since mariadb-dump normally reads the [client] and [mariadb-dump] (or [mysqldump]) groups, --defaults-group-suffix=x would cause it to also read the groups [mariadb-dump_x] (or [mysqldump_x]) and [client_
Insert rows with instead of .
On a primary replication server, delete the binary logs by sending a statement to the server after performing the dump operation. This option automatically enables --master-data=2.
Parallel dump of multiple databases. Works just like --tab, with regard to output (sql file for table definition and tab-separated for data, same options, for example, --parallel). It also allows the --databases and --all-databases options. When --dir is used, it creates the directory structure in the output directory pointed to by --dir. For every database to be dumped, there is a directory with the database name. All options that --tab supports are also supported by --dir, in particular --parallel. This option is available from MariaDB 11.5.
'/*!40000 ALTER TABLE`` ``tb_name``DISABLE KEYS``/; and '/!40000 ALTER TABLE`` ``tb_name`` ``ENABLE KEYS */; are written to the output. This makes loading the dump file faster, because the indexes are created after all rows are inserted. This option is effective only for non-unique indexes of MyISAM tables. Disable with --skip-disable-keys.
If the --comments option and this option are 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 . This option is available from MariaDB 10.11. Until this option was introduced, 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 replica server that can be used to set up another replica server with the same primary. Causes the position and filename of the primary to be appended to the dumped data output. Setting the value to 1 (the default) prints it as a command in the dumped data output; if set to 2, that command is prefixed with a comment symbol. This option will turn on --lock-all-tables, 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. Make sure to read about --single-transaction below). In all cases, any action on logs happens at the exact moment of the dump. This option automatically turns off --lock-tables.
This option pauses any running SQL threads during the dump.
This option stops any running SQL threads before the dump, and restarts all stopped IO and SQL threads after completion.
Include for the dumped databases in the output.
Use multiple-row syntax that include several values lists. This results in a smaller dump file and speeds up inserts when the file is reloaded. Defaults to ON; use --skip-extended-insert to disable.
Fields in the output file are terminated by the given string. Used with the --tab option and has the same meaning as the corresponding FIELDS clause for .
Fields in the output file are enclosed by the given character. Used with the --tab option and has the same meaning as the corresponding FIELDS clause for .
Fields in the output file are optionally enclosed by the given character. Used with the --tab option and has the same meaning as the corresponding FIELDS clause for .
Fields in the output file are escaped by the given character. Used with the --tab option and has the same meaning as the corresponding FIELDS clause for .
Removed in MariaDB 5.5. Use --lock-all-tables instead.
Flush the MariaDB server log files before starting the dump. This option requires the . If you use this option in combination with the --databases= or --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 all tables are locked. If you want your dump and the log flush to happen at the same exact moment, you should use --flush-logs together with either --lock-all-tables or --master-data.
Send a statement to the server after dumping the . 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 in this example, 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.
Used together with --master-data and --dump-slave to more conveniently set up a new replica. It causes those options to output SQL statements that configure the replica to use the to connect to the primary 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.
Display a help message and exit.
Dump binary strings in hexadecimal format (for example, ´abc´ becomes 0x616263). The affected data types are , , the types, and .
Connect to and dump data from the MariaDB or MySQL server on the given host. The default host is localhost.
Do not dump the specified database. To specify more than one database to ignore, use the directive multiple times, once for each database. Only takes effect when used together with --all-databases or -A.
Do not dump the specified table. To specify more than one table to ignore, use the directive multiple times, once for each table. Each table must be specified with both database and table names, for example, --ignore-table=database.table. This option also can be used to ignore views.
Do not dump the specified table data (only the structure). To specify more than one table to ignore, use the directive multiple times, once for each table. Each table must be specified with both database and table names. See also --no-data.
Add the MASTER_HOST and MASTER_PORT options for the statement when using the --dump-slave option for a replica dump.
Insert rows with INSERT IGNORE instead of INSERT.
Lines in the output file are terminated by the given string. This option is used with the --tab option and has the same meaning as the corresponding LINES clause for .
Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump by executing . 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 tables. For transactional tables such as , --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 no logging.
When restoring the dump, if logging is turned on, the server logs queries to the general and . Defaults to ON; use --skip-log-queries to disable.
Causes the position and filename to be appended to the output, useful for dumping a primary replication server to produce a dump file that can be used to set up another server as a replica of the primary. These are the primary server coordinates from which the replica should start replicating after you load the dump file into the replica.
If the option is set to 1 (the default), print it as a command; if set to 2, that command is prefixed with a comment symbol. This --master-data option turns --lock-all-tables on, unless --single-transaction is specified, too. In all cases, any action on logs will happen at the exact moment of the dump. This option automatically turns --lock-tables off. In all cases, any action on logs happens at the exact moment of the dump. It is also possible to set up a replica by dumping an existing replica of the primary. To do this, use the following procedure on the existing replica:
Stop the SQL thread of the replica and get its current status.
From the output of the SHOW REPLICA STATUS statement, the binary log coordinates of the primary server from which the new replica should start replicating are the values of the Relay_Master_Log_File and Exec_Master_Log_Pos fields. Denote those values as file_name and file_pos.
The maximum packet length to send to or receive from server. The maximum is 1GB.
Sets the maximum time any statement can run before being timed out by the server. Default value is 0 (no limit).
The initial buffer size for client/server TCP/IP and socket communication. This can be used to limit the size of rows in the dump. When creating multiple-row INSERT statements (as with the --extended-insert or --opt option), mariadb-dump creates rows up to net_buffer_length length.
Enclose the statements for each dumped table within and statements. ON by default from MariaDB 11.8 to allow faster data loading by InnoDB, writing only one undo log for the whole operation.
This option suppresses the statement that normally is output for each dumped database if --all-databases or --databases is given.
Do not write statements which 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 statement for the table (for example, to create an empty copy of the table by loading the dump file). See also --ignore-table-data.
Do not dump rows for engines that manage external data (for instance, , MRG_ISAM, , , , VP, ). This option is enabled by default. If you want to dump data for these engines, you need to set --no-data-med=0.
Don't read default options from any option file. Must be given as the first argument.
Suppress the SET NAMES statement. 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, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys. Enabled by default, disable with --skip-opt. 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
Sorts each table's rows by primary key, or first unique key, if such a key exists. This is useful when dumping a table to be loaded into an table, but will make the dump itself 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 'Table definition has changed, please retry transaction'. This option is available from MariaDB 10.9.1.
Number of dump table jobs executed in parallel (only for use with the --tab option). 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 the disk becomes the bottleneck, after which adding more parallel jobs does not bring better performance. From MariaDB 11.4.1.
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.
Print the program argument list and exit. Must be given as the first argument.
The connection protocol to use for connecting to the server (TCP, SOCKET, PIPE, MEMORY). 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 and to then dump the results directly to stdout rather than retrieving the entire row set and buffering it in memory before writing it out. Defaults to ON, use --skip-quick to disable.
Quote identifiers (such as database, table, and column names) within backtick (`) characters. If the ANSI_QUOTES SQL mode is enabled, identifiers are quoted with (") 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.
Use statements instead of 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.
Include stored routines ( and ) for the dumped databases in the output. Use of this option requires the SELECT privilege for the table. The output generated using --routines contains and 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 are 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 table directly, using a MariaDB account which has appropriate privileges for the mysql database.
Add 'SET NAMES default_character_set' to the output in order to set the . Enabled by default; suppress with --skip-set-charset.
Change the value of a variable. This option is deprecated; you can set variables directly with --variable-name=value.
Shared-memory name to use for Windows connections using shared memory to a local server (started with the --shared-memory option). Case-sensitive. Defaults to MYSQL.
This option sends a SQL statement to the server before dumping data. It is useful only with transactional tables such as , 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. The single-transaction feature depends not only on the engine being transactional and capable of REPEATABLE-READ, but also on START TRANSACTION WITH CONSISTENT SNAPSHOT. The dump is not guaranteed to be consistent for other storage engines. For example, any , or 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: , , , , or . A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the SELECT (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
Disable the --add-locks option.
Disable the --comments option.
Disable the --disable-keys option.
Disable the --extended-insert option.
Disable the --opt option (disables --add-drop-table, --add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys).
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.
Enables . TLS is also enabled even without setting this option when certain other TLS options are set. The --ssl option does not enable by default. In order to verify the server certificate, the user must specify the --ssl-verify-server-cert option.
Defines a path to a PEM file that should contain one or more X509 certificates for trusted Certificate Authorities (CAs) to use for . This option requires that you use the absolute path, not a relative path. See for more information. This option implies the --ssl option.
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 . This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the command. See for more information. This option is only supported if the client was built with OpenSSL or yaSSL. If the client was built with GnuTLS or Schannel, then this option is not supported. See for more information about which libraries are used on which platforms. This option implies the --ssl option.
Defines a path to the X509 certificate file to use for . This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
List of permitted ciphers or cipher suites to use for . This option implies the --ssl option.
Defines a path to a PEM file that should contain one or more revoked X509 certificates to use for . This option requires that you use the absolute path, not a relative path. See for more information. This option is only supported if the client was built with OpenSSL or Schannel. If the client was built with yaSSL or GnuTLS, then this option is not supported. See for more information about which libraries are used on which platforms.
Defines a path to a directory that contains one or more PEM files that should each contain one revoked X509 certificate to use for . This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the command. See for more information. This option is only supported if the client was built with OpenSSL. If the client was built with yaSSL, GnuTLS, or Schannel, then this option is not supported. See for more information about which libraries are used on which platforms.
Defines a path to a private key file to use for . This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
Enables . This option is disabled by default.
Dump the database's system tables in a logical form. With this option, the tables are dumped as , and other forms of logical portable SQL statements. The option values here are from the set of all, users, plugins, udfs, servers, stats, timezones.
Produce tab-separated text-format data files. With this option, for each dumped table, mariadb-dump creates a tbl_name.sql file containing the CREATE TABLE statement that creates the table, and a tbl_name.txt file containing the table's data. The option value is the directory in which to write the files. Note: This option can only be used when mariadb-dump is run on the same machine as the mariadbd server. You must have the FILE privilege, and the server must have permission to write files in the directory that you specify. By default, the .txt data files are formatted using tab characters between column values, and a newline at the end of each line. The format can be specified explicitly using the --fields-xxx and --lines-terminated-by
This option overrides the --databases (-B) option. mariadb-dump regards all name arguments following the option as table names.
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. See for more information.
Include for each dumped table in the output. This option is enabled by default; disable it with --skip-triggers.
This option enables 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 is doing during various stages.
Output 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. Example:
--where="user = ´jimf´" -w"userid > 1" -w"userid < 1" .
Usage of wildcards in the table/database name. Without the --databases option, wildcards can be used only in tables names. From .
Dump a database as well-formed XML.
Some mariadb-dump options are shorthand for groups of other options:
Use of --opt is the same as specifying--add-drop-table, --add-locks,--create-options, --disable-keys,--extended-insert, --lock-tables,--quick, and --set-charset. All of the
options that --opt stands for also are on by default because --opt
To reverse the effect of a group option, uses its --skip-xxx form (--skip-opt or --skip-compact). It
is also possible to select only part of the effect of a group option by following it with options that enable or disable specific features. Here are some examples:
To select the effect of --opt except for some features, use the --skip option for each feature. To disable extended inserts and memory buffering, use --opt--skip-extended-insert --skip-quick.
(Actually, --skip-extended-insert--skip-quick is sufficient because--opt is on by default.)
To reverse --opt for all features except index disabling and table locking, use --skip-opt--disable-keys
When you selectively enable or disable the effect of a group option, the order is important, because options are processed first to last. For example,--disable-keys --lock-tables--skip-opt would not have the intended effect; it is the same as --skip-opt by itself.
Some options, like --lines-terminated-by, accept a string. The string can be quoted, if necessary. For example, on Unix systems this is the option to enclose fields within double quotes:
An alternative is to specify the hexadecimal value of a character. For example, the following syntax works on any platform:
In addition to reading options from the command line, mariadb-dump can also read options from . If an unknown option is provided to mariadb-dump in an option file, then it is ignored.
The following options relate to how MariaDB command line tools handles option files. They must be given as the first argument on the command line:
mariadb-dump is linked with . However, MariaDB Connector/C does not handle the parsing of option files for this client. That is performed by the server option file parsing code. See for more information.
mariadb-dump reads options from the following from :
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.
XML output from mariadb-dump includes the XML namespace, as shown here :
To restore a backup created with mariadb-dump, use the [mariadb client](../mariadb-client/mariadb-command line-client.md) to import the dump:
You can also set the following variables (--variable-name=value) and boolean options {FALSE|TRUE} by using:
A common use of mariadb-dump is making a backup of an entire database:
You can load the dump file back into the server like this:
Or like this:
mariadb-dump is also very useful for populating databases by copying data from one MariaDB server to another:
It is possible to dump several databases with one command:
To dump all databases, use the --all-databases option:
For InnoDB tables, mariadb-dump provides a way of making an online backup:
This backup acquires a global read lock on all tables (usingFLUSH TABLES WITH READ LOCK) at the beginning of the dump. As soon as this lock has been acquired, the binary log coordinates are read and the lock is released. If long updating statements are running when the FLUSH statement is issued, the MariaDB server may get stalled until those statements finish. After that, the dump becomes lock free and does not disturb reads and writes on the tables. If the update statements that the MariaDB server receives are short (in terms of execution time), the initial lock period should not be noticeable, even with many updates.
For point-in-time recovery (also known as “roll-forward,” when you need to restore an old backup and replay the changes that happened since that backup), it is often useful to rotate the or at least know the binary log coordinates to which the dump corresponds:
Or:
The --master-data and --single-transaction options can be used simultaneously, which provides a convenient way to make an online backup suitable for use prior to point-in-time recovery if tables are
stored that use the InnoDB storage engine.
(video)
(video)
This page is licensed: CC BY-SA / Gnu FDL
x]Dump the replica server.
Restart the replica.
On the new replica, load the dump file.
On the new replica, set the replication coordinates to those of the primary server obtained earlier.
The CHANGE MASTER TO statement might also need other parameters, such as MASTER_HOST to point the replica to the correct primary server host. Add any such parameters as necessary.
--lock-tables. To dump large tables, you should combine the --single-transaction option with --quick.--default-character-setUse of --compact is the same as specifying--skip-add-drop-table,--skip-add-locks, --skip-comments,--skip-disable-keys, and--skip-set-charset options.
--lock-tablesadd-drop-trigger
FALSE
add-locks
TRUE
allow-keywords
FALSE
apply-slave-statements
FALSE
as-of
(No default value)
character-sets-dir
(No default value)
comments
TRUE
compatible
(No default value)
compact
FALSE
complete-insert
FALSE
compress
FALSE
copy-s3-tables
FALSE
create-options
TRUE
databases
FALSE
debug-check
FALSE
debug-info
FALSE
default-character-set
utf8mb4
delayed-insert
FALSE
delete-master-logs
FALSE
disable-keys
TRUE
events
FALSE
extended-insert
TRUE
fields-terminated-by
(No default value)
fields-enclosed-by
(No default value)
fields-optionally-enclosed-by
(No default value)
fields-escaped-by
(No default value)
flush-logs
FALSE
flush-privileges
FALSE
force
FALSE
hex-blob
FALSE
host
(No default value)
include-master-host-port
FALSE
insert-ignore
FALSE
lines-terminated-by
(No default value)
lock-all-tables
FALSE
lock-tables
TRUE
log-error
(No default value)
log-queries
TRUE
master-data
0
max_allowed_packet
16777216
net-buffer-length
1046528
no-autocommit
TRUE (> MariaDB 11.7), FALSE (< MariaDB 11.8)
no-create-db
FALSE
no-create-info
FALSE
no-data
FALSE
no-data-med
TRUE
order-by-primary
FALSE
port
0
quick
TRUE
quote-names
TRUE
replace
FALSE
routines
FALSE
set-charset
TRUE
single-transaction
FALSE
dump-date
TRUE
socket
No default value)
ssl
FALSE
ssl-ca
(No default value)
ssl-capath
(No default value)
ssl-cert
(No default value)
ssl-cipher
(No default value)
ssl-key
(No default value)
ssl-verify-server-cert
FALSE
system
(No default value)
tab
(No default value)
triggers
TRUE
tz-utc
TRUE
user
(No default value)
verbose
FALSE
where
(No default value)
plugin-dir
(No default value)
default-auth
(No default value)
--print-defaults
Print the program argument list and exit.
--no-defaults
Don't read default options from any option file.
--defaults-file=#
Only read default options from the given file #.
--defaults-extra-file=#
Read this file after the global files are read.
--defaults-group-suffix=#
In addition to the default option groups, also read option groups with this suffix.
[mysqldump]
Options read by mariadb-dump, which includes both MariaDB Server and MySQL Server.
[mariadb-dump]
Options read by mariadb-dump.
[client]
Options read by all MariaDB and MySQL client programs, which includes both MariaDB and MySQL clients. For example, mysqldump.
[client-server]
Options read by all MariaDB client programs and the MariaDB Server. This is useful for options like socket and port, which is common between the server and the clients.
[client-mariadb]
Options read by all MariaDB client programs.
NULL (unknown value)
<field name="column_name" xsi:nil="true" />
'' (empty string)
<field name="column_name"></field>
'NULL' (string value)
<field name="column_name">NULL</field>
all
TRUE
all-databases
FALSE
all-tablespaces
FALSE
no-tablespaces
FALSE
add-drop-database
FALSE
add-drop-table
TRUE
mariadb-dump --master-data=2 --all-databases > dumpfileSTART REPLICA;mariadb < dumpfileCHANGE MASTER TO
MASTER_LOG_FILE = ´file_name´,
MASTER_LOG_POS = file_pos;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=[option_list]STOP SLAVE SQL_THREAD;
SHOW REPLICA STATUS;--fields-enclosed-by='"'--fields-enclosed-by=0x22shell> 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>mariadb db_name < backup-file.sqlshell> mariadb-dump db_name > backup-file.sqlshell> mariadb db_name < backup-file.sqlshell> mariadb -e "source /path-to-backup/backup-file.sql" db_nameshell> mariadb-dump --opt db_name | mariadb --host=remote_host -C db_nameshell> mariadb-dump --databases db_name1 [db_name2 ...] > my_databases.sqlshell> mariadb-dump --all-databases > all_databases.sqlshell> mariadb-dump --all-databases --single-transaction all_databases.sqlshell> mariadb-dump --all-databases --master-data=2 > all_databases.sqlshell> mariadb-dump --all-databases --flush-logs --master-data=2 > all_databases.sqlmariadb-hotcopy is a Perl script that was originally written and contributed by Tim Bunce. It uses FLUSH TABLES, LOCK TABLES, and cp or scp to make a database backup.
It is a fast way to make a backup of the database or single tables, but it can be run only on the same machine where the database directories are located. mariadb-hotcopy works only for backing up MyISAM and ARCHIVE tables. It runs on Unix and NetWare.
To use mariadb-hotcopy, you must have read access to the files for the tables that you are backing up, the SELECT for those tables, the RELOAD privilege (to be able to execute FLUSH TABLES), and the LOCK TABLES privilege (to be able to lock the tables).
Back up tables in the given database that match a regular expression:
The regular expression for the table name can be negated by prefixing it with a tilde (~):
mariadb-hotcopy supports the following options, which can be specified on the command line or in the [mariadb-hotcopy] and [client] option file groups.
--help, -?Display a help message and exit.
--addtodestDo not rename target directory (if it exists); merely add files to it.
--allowoldDo not abort if a target exists; rename it by adding an _old suffix.
--checkpoint=db_name.tbl_nameInsert checkpoint entries into the specified database db_name and table tbl_name.
--chroot=directoryBase directory of the chroot jail in which mariadbd operates. The path value should match that of the
--chroot option given to mariadbd.
--debugEnable debug output.
--dryrun, -nReport actions without performing them.
--flushlogFlush logs after all tables are locked.
--host=host_name, -h host_nameThe host name of the local host to use for making a TCP/IP connection to the local server. By default, the connection is made to localhost using a Unix socket file.
--keepoldDo not delete previous (renamed) target when done.
--method=methodThe method for copying files (cp or scp). The default is cp.
--noindicesDo not include full index files for MyISAM tables in the backup. This makes the backup smaller and faster. The indexes for reloaded tables can be reconstructed later with .
--old-serverConnect to old MySQL server (before MySQL 5.5) which doesn't have fully implemented.
--password=password, -ppasswordThe password to use when connecting to the server. The password value is mandatory for this option, unlike for other MariaDB programs. 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.
--port=port-number, -P port-numberThe TCP/IP port number to use when connecting to the local server.
--quiet, -qBe silent except for errors.
--record\_log\_pos=db_name.tbl_nameRecord master and slave status in the specified database db_name and table tbl_name.
--regexp=expressionCopy all databases with names that match the given regular expression.
--resetmasterReset the binary log after locking all the tables.
--resetslaveReset the master.info file after locking all the tables.
--socket=socket-file, -S socket-fileThe Unix socket file to use for connections to localhost.
--suffix=stringThe suffix string to use for names of copied databases.
--tmpdir=directoryThe temporary directory. The default is /tmp.
--user=username, -u usernameThe MariaDB username to use when connecting to the server.
Use perldoc for additional mariadb-hotcopy documentation, including information about the structure of the tables needed for the--checkpoint and ``--record_log_pos options:
This page is licensed: CC BY-SA / Gnu FDL
shell> mariadb-hotcopy db_name [/path/to/new_directory]
shell> mariadb-hotcopy db_name_1 ... db_name_n /path/to/new_directoryshell> mariadb-hotcopy db_name./regex/shell> mariadb-hotcopy db_name./~regex/shell> perldoc mariadb-hotcopyWithout a doubt, you want your backup/restore and export/import operations to be fast, easy, and automated wherever possible. You can have it all that way with dbForge Studio for MySQL. As the name implies, it is an IDE for MySQL development, management, and administration, yet it works just as perfectly as a MariaDB GUI client. Now, let's see how it tackles routine database backups.
On the Database menu, go to Backup and Restore, and click Backup Database to open Database Backup Wizard.
On the General page, specify the required connection and database, the path for the backup file to be saved to, and the output file name in the respective fields. Optionally, you can append a timestamp to the file name, enable the auto-deletion of old files, and compress your backup into an archive. After you set it all up, click Next.
On the Backup content page, select the content for your backup and click Next.
On the Options page, configure your detailed backup options—there are quite a few of those to match your requirements most precisely. Then click Next.
On the Errors handling page, configure the Errors handling and Log settings options. Afterwards, click Backup to run the backup process.
Note that you have two more options here: you can select Save Project to save your current backup project with all the settings—or you can select Save Command Line to save a backup script that you can execute from the command line whenever you need.
After you click Backup, wait for the backup process to be completed.
Note that you don't have to go through every wizard page to click Backup. You can do it whenever you've finished configuring your settings.
Finally, confirm the successful completion by clicking Finish.
As you can see, it's very easy. Furthermore, you can schedule to run regular backups using Action > Create Basic Task in Windows Task Scheduler.
This is an even faster task, done in half as many steps.
On the Database menu, go to *Backup and Restore, and click Restore Database to open the Database Restore Wizard.
On the Database Script File page, specify the required connection and database, as well as the path to the previously saved backup file.
After that, click Restore, and let the Studio do the rest for you.
And when it's done, click Finish, and there you have it.
You can learn more about this functionality on the dedicated . Please note: while the page focuses on MySQL databases, everything that's described there is just as perfectly applicable to MariaDB from the same Studio with the same workflow.
With dbForge Studio, you can export data to 14 most popular formats: HTML, TXT, XLS, XLSX, MDB, RTF, PDF, JSON, XML, CSV, OBSC, DBF, SQL, and Google Sheets. You can do it with an easy-to-follow wizard that guides you through the entire process and delivers quite a few customization options.
Let's see how it works. And before we start, note that different formats may have slightly different wizard pages. In our walkthrough, we'll take the HTML format as an example.
To open the export wizard, on the Database menu, click Export Data.
On the Export format page, pick the required format and click Next.
On the Source page, select the required connection, database, as well as tables and views to be exported. Then click Next.
On the Output settings page, specify the path for the output, select to export data into a single or several separate files, and configure a few other settings, such as timestamps and compression. Then click Next.
On the Options page, configure and preview table grid options for exported data. Click Next.
On the Data formats page, you have two tabs. On the Columns tab, you can check the list of columns to be exported.
Then, on the Formats tab, you can adjust the default format settings for Date, Time, Date Time, Currency, Float, Integer, Boolean, Null String, as well as select the required binary encoding.
Once you make sure everything is correct, click Next.
On the Exported rows page, select to export all rows or define a certain range of rows, and then click Next*.**
On the Errors handling page, configure the errors handling behavior and select to keep a log file, if necessary.
But before you click Export, note that you can save templates with your settings for recurring export operations. To do that, click Save in the lower left corner of the wizard, specify a name and a destination for the template file to be saved to, and then click Save.
Also note that you don't have to go through every wizard page to click Export. You can do it whenever you've finished configuring your settings.
Finally, after you click Export, watch the progress and click Finish upon completion.
Done! Now, if you want, you can open the folder with the output file right away.
dbForge Studio supports 10 data formats for import, including TXT, XLS, XLSX, MDB, XML, JSON, CSV, ODBC, DBF, and Google Sheets. Just like with export, you have a helpful wizard at hand, whose pages may have differences, depending on the format. And let's pick a different format this time, say, the Microsoft Excel format (XLS).
To open the wizard, on the Database menu, click Import Data.
On the Source file page, choose the required format, select the file to import data from, and click Next.
On the Destination page, select the target connection and database. Then you can select to import data either to a new table or to an existing table. Click Next.
On the Options page, configure and preview table grid options for imported data. Click Next.
On the Data formats page, you have two tabs. The first tab is called Common Formats, where you can specify the required formats for null strings, thousand and decimal separators, boolean variables, date and time.
The second tab is called Column Settings, where you can configure format settings for separate columns.
Once you make sure everything is correct, click Next.
On the Mapping page, you can map the source columns to the target ones and preview the results. If you're importing data into a new table, the Studio will automatically create and map all the columns, so you will only have to make adjustments if you wish. Then click Next.
On the Modes page, select one of the 5 available import modes and click Next.
On the Output page, select the preferred output option and click Next.
On the Errors handling page, configure the errors handling behavior and select to keep a log file, if necessary.
Similarly to export, you can save templates with your settings for recurring import operations. To do that, click Save in the lower left corner of the wizard, specify a name and a destination for the template file to be saved to, and then click Save.
Also note that you don't have to go through every wizard page to click Import. You can do it whenever you've finished configuring your settings.
After you click Import, wait for the process to be completed. Then click Finish to confirm the successful completion, and check the results if you wish. That's it!
You can learn more about this functionality on the dedicated . Please note: while the page focuses on MySQL databases, everything that's described there is just as perfectly applicable to MariaDB from the same Studio with the same workflow.
There is much more to dbForge Studio when it comes to MariaDB development and management. You can have a brief overview of its features and capabilities on .
That said, if you'd love to have a single IDE that doesn't need any 3rd-party extensions because it can perfectly deal with nearly any task on its own, feel free to and give it a go in your daily work.
This page is licensed: CC BY-SA / Gnu FDL
mariadb-import loads tables from text files in various formats.
mariadb-import loads tables from text files in various formats. The base name of the text file must be the name of the table that should be used. If one uses sockets to connect to the MariaDB server, the server will open and read the text file directly. In other cases the client will open the text file. The SQL statement LOAD DATA INFILE is used to import the rows.
The command to use mariadb-import and the general syntax is:
mariadb-import supports the following options:
--character-sets-dir=directoryDirectory for character set files.
-c cols, --columns=colsUse only these columns to import the data to. Give the column names in a comma separated list. This is same as giving columns to .
-C, --compressUse compression in server/client protocol.
--database=databaseRestore the specified database, ignoring others.To specify more than one database to include, use the directive multiple times, once for each database. Only takes effect when used together with the --dir option. This option is available from MariaDB 11.6.
--debug[=options]Output debug log. Often this is d:t:o,filename. The default is d:t:o.
--debug-checkCheck memory and open file usage at exit.
--debug-infoPrint some debug info at exit.
--default-auth=pluginDefault authentication client-side plugin to use.
--default-character-set=character-setSet the default .
--defaults-extra-file=fileRead this file after the global files are read. Must be given as the first option.
--defaults-file=fileOnly read default options from the given file name Must be given as the first option.
--defaults-group-suffix=group-suffixIn addition to the given groups, also read groups with this suffix.
-d, --deleteFirst delete all rows from table.
--dir=directoryRestore all tables from backup directory created using . This option is available from MariaDB 11.6.
--fields-terminated-by=stringFields in the input file are terminated by the given string.
--fields-enclosed-by=characterFields in the import file are enclosed by the given character.
--fields-optionally-enclosed-by=characterFields in the input file are optionally enclosed by the given character.
--fields-escaped-by=characterFields in the input file are escaped by the given character.
-f, --forceContinue even if we get an SQL error.
-?, --helpDisplay this help and exits.
-h host, --host=hostConnect to host.
-i, --ignoreIf duplicate unique key was found, keep old row.
-k, --ignore-foreign-keysDisable foreign key checks while importing the data.
--ignore-database=databaseDo not restore the specified database. To specify more than one database to ignore, use the directive multiple times, once for each database. Only takes effect when used together with the --dir option. This option is available from MariaDB 11.6.
--ignore-lines=nIgnore first n lines of data infile.
--ignore-table=tableDo not restore the specified table. To specify more than one table to ignore, use the directive multiple times, once for each table. Each table must be specified with both database and table names, for instance, --ignore-table=database.table. Only takes effect when used together with the --dir option. This option is available from MariaDB 11.6.
--innodb-optimize-keysCreate secondary indexes after data load, which speeds up loading (InnoDB only). Defaults to on; use
--skip-innodb-optimize-keys to disable. This option is available from MariaDB 11.8.
--lines-terminated-by=stringLines in the input file are terminated by the given string.
-L, --localRead all files through the client.
-l, --lock-tablesLock all tables for write (this disables threads).
--low-priorityUse LOW_PRIORITY when updating the table.
--no-defaultsDon't read default options from any option file. Must be given as the first option.
-j, --parallel=numberNumber of LOAD DATA jobs executed in parallel. This option is available from MariaDB 11.4.1. --use-threads is a synonym.
-ppassword, --passwordpasswordPassword to use when connecting to server. If password is not given, it's asked from the terminal. 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.
--pipe, -Wn Windows, connect to the server via a named pipe. This option applies only if the server supports named-pipe connections.
--plugin-dirDirectory for client-side plugins.
-P port-number, --port=port-numberPort number to use for connection or 0 for default to, in order of preference, my.cnf, the MYSQL_TCP_PORT , /etc/services. Default is 3306.
--print-defaultsPrint the program argument list and exit. Must be given as the first option.
--protocol=protocolThe protocol to use for connection (tcp, socket, pipe, memory).
-r, --replaceIf duplicate unique key was found, replace old row.
--shared-memory-base-nameShared-memory name to use for Windows connections using shared memory to a local server (started with the --shared-memory option). Case sensitive.
-s, --silentSilent mode. Produce output only when errors occur.
-S, --socket={socket|named-pipe}For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
--sslEnables . TLS is also enabled even without setting this option when certain other TLS options are set. The --ssl option does not enable by default. In order to verify the server certificate, the user must specify the --ssl-verify-server-cert option.
--ssl-ca=pem-fileDefine a path to a PEM file that should contain one or more X509 certificates for trusted Certificate Authorities (CAs) to use for . This option requires that you use the absolute path, not a relative path. See for more information. This option implies the --ssl option.
--ssl-capath=pem-directoryDefine 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 . This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the command. See for more information. This option is only supported if the client was built with OpenSSL or yaSSL. If the client was built with GnuTLS or Schannel, then this option is not supported. See for more information about which libraries are used on which platforms. This option implies the --ssl option. |
--ssl-cert=fileDefine a path to the X509 certificate file to use for . This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
--ssl-cipher=cipher-listList of permitted ciphers or cipher suites to use for . This option implies the --ssl option.
--ssl-crl=pem-fileDefines a path to a PEM file that should contain one or more revoked X509 certificates to use for . This option requires that you use the absolute path, not a relative path. See for more information. This option is only supported if the client was built with OpenSSL or Schannel. If the client was built with yaSSL or GnuTLS, then this option is not supported. See for more information about which libraries are used on which platforms.
--ssl-crlpath=pem-directoryDefine a path to a directory that contains one or more PEM files that should each contain one revoked X509 certificate to use for . This option requires that you use the absolute path, not a relative path. The directory specified by this option needs to be run through the command. See for more information. This option is only supported if the client was built with OpenSSL. If the client was built with yaSSL, GnuTLS, or Schannel, then this option is not supported. See for more information about which libraries are used on which platforms.
--ssl-key=key-fileDefine a path to a private key file to use for . This option requires that you use the absolute path, not a relative path. This option implies the --ssl option.
--ssl-verify-server-certEnable . This option is disabled by default.
--table=tableRestore the specified table ignoring others. Use --table=dbname.tablename with this option. To specify more than one table to include, use the directive multiple times, once for each table. Only takes effect when used together with the --dir option. This option is available from MariaDB 11.6.
--tls-version=tls-listThis 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. See for more information.
--use-threads=numberLoad files in parallel. The argument is the number of threads to use for loading data. From , a synonym for -j, --parallel=num.
-u username, --user=usernameUser for login if not current user.
-v, --verbosePrint info about the various stages.
-V, --versionOutput version information and exit.
In addition to reading options from the command line, mariadb-import can also read options from . If an unknown option is provided to mariadb-import in an option file, then it is ignored.
The following options relate to how MariaDB command line tools handles option files. They must be given as the first argument on the command line:
mariadb-import is linked with MariaDB Connector/C. Therefore, it may be helpful to see for more information on how MariaDB Connector/C handles option files.
mariadb-import reads options from the following from :
This page is licensed: CC BY-SA / Gnu FDL
delete
FALSE
fields-terminated-by
(No default value)
fields-enclosed-by
(No default value)
fields-optionally-enclosed-by
(No default value)
fields-escaped-by
(No default value)
force
FALSE
host
(No default value)
ignore
FALSE
ignore-lines
0
lines-terminated-by
(No default value)
local
FALSE
lock-tables
FALSE
low-priority
FALSE
port
3306
replace
FALSE
silent
FALSE
socket
/var/run/mysqld/mysqld.sock
ssl
FALSE
ssl-ca
(No default value)
ssl-capath
(No default value)
ssl-cert
(No default value)
ssl-cipher
(No default value)
ssl-key
(No default value)
ssl-verify-server-cert
FALSE
use-threads
0
user
(No default value)
verbose
FALSE
--print-defaults
Print the program argument list and exit.
--no-defaults
Don't read default options from any option file.
--defaults-file=#
Only read default options from the given file #.
--defaults-extra-file=#
Read this file after the global files are read.
[mysqlimport]
Options read by mysqlimport, which includes both MariaDB Server and MySQL Server.
[mariadb-import]
Options read by mysqlimport.
[client]
Options read by all MariaDB and MySQL client programs, which includes both MariaDB and MySQL clients. For example, mysqldump.
[client-server]
Options read by all MariaDB client programs and the MariaDB Server. This is useful for options like socket and port, which is common between the server and the clients.
[client-mariadb]
Options read by all MariaDB client programs.
character-sets-dir
(No default value)
default-character-set
latin1
columns
(No default value)
compress
FALSE
debug-check
FALSE
debug-info
FALSE
mariadb-import [OPTIONS] database textfile1 [textfile2 ...]