Options for mariadb-dump & mysqldump in MariaDB Community Server 10.5
mariadb-dump utility is the newer name for
mysqldump, though you can still run it using either name.
Add a DROP DATABASE before each create.
Add a DROP TABLE before each create. (Defaults to on; use --skip-add-drop-table to disable.)
Add a DROP TRIGGER before each create.
Add locks around INSERT statements. (Defaults to on; use --skip-add-locks to disable.)
Dump all the databases. This will be same as --databases with all databases selected.
Dump all the tablespaces.
Allow creation of column names that are keywords.
Adds 'STOP SLAVE' prior to 'CHANGE MASTER' and 'START SLAVE' to bottom of dump.
Directory for character set files.
Write additional information. (Defaults to on; use --skip-comments to disable.)
Give less verbose output (useful for debugging). Disables structure comments and header/footer constructs. Enables options --skip-add-drop-table --skip-add-locks --skip-comments --skip-disable-keys --skip-set-charset.
Change the dump to be compatible with a given mode. By default tables are dumped in a format optimized for MariaDB. Legal modes are: ansi, mysql323, mysql40, postgresql, oracle, mssql, db2, maxdb, no_
Use complete insert statements.
Use compression in server/client protocol.
If 'no' S3 tables will be ignored, otherwise S3 tables will be copied as Aria tables and then altered to S3
Include all MariaDB specific create options. (Defaults to on; use --skip-create-options to disable.)
Dump several databases. Note the difference in usage; in this case no tables are given. All name arguments are regarded as database names. 'USE db_
This is a non-debug version. 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 character set.
Read this file after the global files are read.
Only read default options from the given file #.
Additionally read default groups with # appended as a suffix.
Insert rows with INSERT DELAYED.
Delete logs on master after backup. This automatically enables --master-data.
'/*!40000 ALTER TABLE tb_
Put a dump date to the end of the output. (Defaults to on; use --skip-dump-date to disable.)
This causes the binary log position and filename of the master to be appended to the dumped data output. Setting the value to 1, will printit as a CHANGE MASTER command in the dumped data output; if equal 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.
Use multiple-row INSERT syntax that include several VALUES lists. (Defaults to on; use --skip-extended-insert to disable.)
Fields in the output file are enclosed by the given character.
Fields in the output file are escaped by the given character.
Fields in the output file are optionally enclosed by the given character.
Fields in the output file are terminated by the given string.
Flush logs file in server before starting dump. Note that if you dump many databases at once (using the option --databases= or --all-databases), the logs will be flushed for each database dumped. The exception is when using --lock-all-tables or --master-data: in this case the logs will be flushed only once, corresponding to the moment all tables are locked. So if you want your dump and the log flush to happen at the same exact moment you should use --lock-all-tables or --master-data with --flush-logs.
Emit a FLUSH PRIVILEGES statement 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 restore.
Continue even if we get an SQL error.
Used together with --master-data=1 or --dump-slave=1.When enabled, the output from those options will set the GTID position instead of the binlog file and offset; the file/offset will appear only as a comment. When disabled, the GTID position will still appear in the output, but only commented.
Display this help message and exit.
Dump binary strings (BINARY, VARBINARY, BLOB) in hexadecimal format.
Connect to host.
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|-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, e.g., --ignore-table=database.table.
Do not dump the specified table data. 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, e.g., --ignore-table-data=database.table.
Insert rows with INSERT IGNORE.
Lines in the output file are terminated by the given string.
Locks all tables across all databases. This is achieved by taking a global read lock for the duration of the whole dump. Automatically turns --single-transaction and --lock-tables off.
Lock all tables for read. (Defaults to on; use --skip-lock-tables to disable.)
Append warnings and errors to given file.
When restoring the dump, the server will, if logging turned on, log the queries to the general and slow query log. (Defaults to on; use --skip-log-queries to disable.)
This causes the binary log position and filename to be appended to the output. If equal to 1, will print it as a CHANGE MASTER command; if equal 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 (on servers before MariaDB 5.3 this will still take a global read lock for 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.
The maximum packet length to send to or receive from server.
Max statement execution time. If unset, overrides server default with 0.
The buffer size for TCP/IP and socket communication.
Wrap tables with autocommit/commit statements.
Suppress the CREATE DATABASE ... IF EXISTS statement that normally is output for each dumped database if --all-databases or --databases is given.
Don't write table creation info.
No row information.
No row information for engines that Manage External Data (MRG_
Don't read default options from any option file.
Same as --skip-set-charset.
Do not dump any tablespace information.
Same as --add-drop-table, --add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys. Enabled by default, disable with --skip-opt.
Sorts each table's rows by primary key, or first unique key, if such a key exists. Useful when dumping a MyISAM table to be loaded into an InnoDB table, but will make the dump itself take considerably longer.
Password to use when connecting to server. If password is not given it's solicited on the tty.
Directory for client-side plugins.
Port number to use for connection.
Print the program argument list and exit.
The protocol to use for connection (tcp, socket, pipe).
Don't buffer query, dump directly to stdout. (Defaults to on; use --skip-quick to disable.)
Quote table and column names with backticks (`). (Defaults to on; use --skip-quote-names to disable.)
Use REPLACE INTO instead of INSERT INTO.
Direct output to a given file. This option should be used in systems (e.g., DOS, Windows) that use carriage-return linefeed pairs (\r\n) to separate text lines. This option ensures that only a single newline is used.
Dump stored routines (functions and procedures).
Add 'SET NAMES default_
Creates a consistent snapshot by dumping all tables in a single transaction. Works ONLY for tables stored in storage engines which support multiversioning (currently only InnoDB does); the dump is NOT guaranteed to be consistent for other storage engines. While a --single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log position), no other connection should use the following statements: ALTER TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE, as consistent snapshot is not isolated from them. Option automatically turns off --lock-tables.
Disable --opt. Disables --add-drop-table, --add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys.
The socket file to use for connection.
Enable SSL for connection (automatically enabled with other flags).
CA file in PEM format (check OpenSSL docs, implies --ssl).
CA directory (check OpenSSL docs, implies --ssl).
X509 cert in PEM format (implies --ssl).
SSL cipher to use (implies --ssl).
Certificate revocation list (implies --ssl).
Certificate revocation list path (implies --ssl).
X509 key in PEM format (implies --ssl).
Verify server's "Common Name" in its cert against hostname used when connecting. This option is disabled by default.
Dump system tables as portable SQL. Any combination of: all, users, plugins, udfs, servers, stats, timezones
Create tab-separated textfile for each table to given path. (Create .sql and .txt files.) NOTE: This only works if mysqldump is run on the same machine as the mysqld server.
Overrides option --databases (-B).
TLS protocol version for secure connection.
Dump triggers for each dumped table. (Defaults to on; use --skip-triggers to disable.)
User for login if not current user.
Print info about the various stages.
Output version information and exit.
Dump only selected records. Quotes are mandatory.
Dump a database as well formed XML.