Supported Backup Options
This page lists all of the mysqldump options that can be passed to Ark Backups when creating a backup.
Important
While Ark Backups supports these options, they may not be supported by all MySQL/MariaDB servers and they are NOT guaranteed to work with every individual database. Every user's data is unique. A good rule of thumb, is that if you can use the options successfully with mysqldump on your own, it should work with us.
Options that require specifying a value should be separated from that value by an = character.
For example: --set-gtid-purged=OFF
| Option | Description | Values |
|---|---|---|
| --add-drop-database | Add DROP DATABASE statement before each CREATE DATABASE statement | |
| --add-drop-table | Add DROP TABLE statement before each CREATE TABLE statement | |
| --add-drop-trigger | Add DROP TRIGGER statement before each CREATE TRIGGER statement | |
| --add-locks | Surround each table dump with LOCK TABLES and UNLOCK TABLES statements | |
| --allow-keywords | Allow creation of column names that are keywords | |
| --compact | Produce more compact output | |
| --complete-insert | Use complete INSERT statements that include column names | |
| --compression-algorithms | Permitted compression algorithms for connections to server | zlib, zstd, uncompressed |
| --create-options | Include all MySQL-specific table options in CREATE TABLE statements | |
| --events | Dump events from dumped databases | |
| --extended-insert | Use multiple-row INSERT syntax | |
| --flush-privileges | Emit a FLUSH PRIVILEGES statement after dumping mysql database | |
| --force | Continue even if an SQL error occurs during a table dump | |
| --insert-ignore | Write INSERT IGNORE rather than INSERT statements | |
| --lock-all-tables | Lock all tables across all databases | |
| --lock-tables | Lock all tables before dumping them | |
| --no-autocommit | Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements | |
| --no-create-db | Do not write CREATE DATABASE statements | |
| --no-create-info | Do not write CREATE TABLE statements that re-create each dumped table | |
| --no-data | Do not dump table contents | |
| --no-tablespaces | Do not write any CREATE LOGFILE GROUP or CREATE TABLESPACE statements in output | |
| --quick | Retrieve rows for a table from the server a row at a time | |
| --replace | Write REPLACE statements rather than INSERT statements | |
| --routines | Dump stored routines (procedures and functions) from dumped databases | |
| --set-gtid-purged | Whether to add SET @@GLOBAL.GTID_PURGED to output | ON, OFF, AUTO |
| --single-transaction | Issue a BEGIN SQL statement before dumping data from server | |
| --skip-comments | Do not add comments to dump file | |
| --skip-opt | Turn off options set by --opt | |
| --verbose | Verbose mode | |
| --zstd-compression-level | Compression level for connections to server that use zstd compression | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22 |