The mysqldump client is a utility that performs logical backups, producing a set of SQL statements that can be run to reproduce the original schema objects, table data, or both. It dumps one or more MySQL database for backup or transfer to another SQL server. The mysqldump command can also generate output in CSV, other delimited text, or XML format.
mysqldump requires at least the
SELECT privilege for dumped tables,
SHOW VIEW for dumped views,
TRIGGER for dumped triggers, and
LOCK TABLES if the
--single-transaction option is not used. Certain options might require other
privileges as noted in the option descriptions.
To reload a dump file, you must have the same privileges needed to create each of the dumped objects by issuing
CREATE statements manually.
mysqldump output can include
ALTER DATABASE statements that change the database collation. These may be used
when dumping stored programs to preserve their character encodings. To reload a dump file containing such
ALTER privilege for the affected database is required.
mysqldump advantages include the convenience and flexibility of viewing or even
editing the output before restoring. You can clone databases for development and DBA work, or produce slight
variations of an existing database for testing. It is not intended as a fast or scalable solution for backing up
substantial amounts of data. With large data sizes, even if the backup step takes a reasonable time, restoring
the data can be very slow because replaying the SQL statements involves disk I/O for insertion, index creation,
and so on.
For large-scale backup and restore, a physical backup is more appropriate, to copy the data files in their original format that can be restored quickly:
If your tables are primarily
InnoDB tables, or if you
have a mix of
consider using the mysqlbackup command of the MySQL
Enterprise Backup product. (Available as part of the Enterprise subscription.) It provides the best
InnoDB backups with minimal disruption; it can also back up
MyISAM and other storage engines; and it provides a number of
convenient options to accommodate different backup scenarios. See
If your tables are primarily
MyISAM tables, consider
using the mysqlhotcopy
instead, for better performance than mysqldump of backup and restore operations. See Section 4.6.10, "mysqlhotcopy
— A Database Backup Program".
mysqldump 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
--opt option (and hence
--quick) is enabled by default, so to enable memory buffering, use
There are in general three ways to use mysqldump—in order to dump a set of one or more tables, a set of one or more complete databases, or an entire MySQL server—as shown here:
mysqldump supports the following options, which can be specified
on the command line or in the
groups of an option file. mysqldump
also supports the options for processing option files described at Section
220.127.116.11, "Command-Line Options that Affect Option-File Handling".
|--add-drop-database||add-drop-database||Add a DROP DATABASE statement before each CREATE DATABASE statement|
|--add-drop-table||add-drop-table||Add a DROP TABLE statement before each CREATE TABLE statement|
|--add-drop-trigger||add-drop-trigger||Add a DROP TRIGGER statement before each CREATE TRIGGER statement|
|--add-locks||add-locks||Surround each table dump with LOCK TABLES and UNLOCK TABLES statements|
|--all-databases||all-databases||Dump all tables in all databases|
|--allow-keywords||allow-keywords||Allow creation of column names that are keywords|
|--apply-slave-statements||apply-slave-statements||Include STOP SLAVE prior to CHANGE MASTER statement and START SLAVE at end of output|
|--bind-address=ip_address||bind-address||Use the specified network interface to connect to the MySQL Server|
|--comments||comments||Add comments to the dump file|
|--compact||compact||Produce more compact output|
|--compatible=name[,name,...]||compatible||Produce output that is more compatible with other database systems or with older MySQL servers|
|--complete-insert||complete-insert||Use complete INSERT statements that include column names|
|--create-options||create-options||Include all MySQL-specific table options in CREATE TABLE statements|
|--databases||databases||Dump several databases|
|--debug[=debug_options]||debug||Write a debugging log|
|--debug-check||debug-check||Print debugging information when the program exits|
|--debug-info||debug-info||Print debugging information, memory and CPU statistics when the program exits|
|--default-auth=plugin||default-auth=plugin||The authentication plugin to use|
|--default-character-set=charset_name||default-character-set||Use charset_name as the default character set|
|--delete-master-logs||delete-master-logs||On a master replication server, delete the binary logs after performing the dump operation|
|--disable-keys||disable-keys||For each table, surround the INSERT statements with statements to disable and enable keys|
|--dump-date||dump-date||Include dump date as "Dump completed on" comment if --comments is given|
|--dump-slave[=value]||dump-slave||Include CHANGE MASTER statement that lists binary log coordinates of slave's master|
|--events||events||Dump events from the dumped databases|
|--extended-insert||extended-insert||Use multiple-row INSERT syntax that include several VALUES lists|
|--fields-enclosed-by=string||fields-enclosed-by||This option is used with the --tab option and has the same meaning as the corresponding clause for LOAD DATA INFILE|
|--fields-escaped-by||fields-escaped-by||This option is used with the --tab option and has the same meaning as the corresponding clause for LOAD DATA INFILE|
|--fields-optionally-enclosed-by=string||fields-optionally-enclosed-by||This option is used with the --tab option and has the same meaning as the corresponding clause for LOAD DATA INFILE|
|--flush-logs||flush-logs||Flush the MySQL server log files before starting the dump|
|--flush-privileges||flush-privileges||Emit a FLUSH PRIVILEGES statement after dumping the mysql database|
|--help||Display help message and exit|
|--hex-blob||hex-blob||Dump binary columns using hexadecimal notation (for example, 'abc' becomes 0x616263)|
|--host||host||Host to connect to (IP address or hostname)|
|--ignore-error=error[,error]...||ignore-error||Ignore the specified errors||5.7.1|
|--ignore-table=db_name.tbl_name||ignore-table||Do not dump the given table|
|--include-master-host-port||include-master-host-port||Include MASTER_HOST/MASTER_PORT options in CHANGE MASTER statement produced with --dump-slave|
|--insert-ignore||insert-ignore||Write INSERT IGNORE statements rather than INSERT statements|
|--lock-all-tables||lock-all-tables||Lock all tables across all databases|
|--lock-tables||lock-tables||Lock all tables before dumping them|
|--log-error=file_name||log-error||Append warnings and errors to the named file|
|--login-path=name||Read login path options from .mylogin.cnf|
|--master-data[=value]||master-data||Write the binary log file name and position to the output|
|--max_allowed_packet=value||max_allowed_packet||The maximum packet length to send to or receive from the server|
|--net_buffer_length=value||net_buffer_length||The buffer size for TCP/IP and socket communication|
|--no-autocommit||no-autocommit||Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements|
|--no-create-db||no-create-db||This option suppresses the CREATE DATABASE statements|
|--no-create-info||no-create-info||Do not write CREATE TABLE statements that re-create each dumped table|
|--no-data||no-data||Do not dump table contents|
|--no-set-names||no-set-names||Same as --skip-set-charset|
|--no-tablespaces||no-tablespaces||Do not write any CREATE LOGFILE GROUP or CREATE TABLESPACE statements in output|
|--opt||opt||Shorthand for --add-drop-table --add-locks --create-options --disable-keys --extended-insert --lock-tables --quick --set-charset.|
|--order-by-primary||order-by-primary||Dump each table's rows sorted by its primary key, or by its first unique index|
|--password[=password]||password||The password to use when connecting to the server|
|--pipe||On Windows, connect to server using a named pipe|
|--plugin-dir=path||plugin-dir=path||The directory where plugins are located|
|--port=port_num||port||The TCP/IP port number to use for the connection|
|--quick||quick||Retrieve rows for a table from the server a row at a time|
|--quote-names||quote-names||Quote identifiers within backtick characters|
|--replace||replace||Write REPLACE statements rather than INSERT statements|
|--result-file=file||result-file||Direct output to a given file|
|--routines||routines||Dump stored routines (procedures and functions) from the dumped databases|
|--set-charset||set-charset||Add SET NAMES default_character_set to output|
|--set-gtid-purged=value||set-gtid-purged||Whether to add SET @@GLOBAL.GTID_PURGED to output|
|--single-transaction||single-transaction||This option issues a BEGIN SQL statement before dumping data from the server|
|--skip-add-drop-table||skip-add-drop-table||Do not add a DROP TABLE statement before each CREATE TABLE statement|
|--skip-add-locks||skip-add-locks||Do not add locks|
|--skip-comments||skip-comments||Do not add comments to the dump file|
|--skip-compact||skip-compact||Do not produce more compact output|
|--skip-disable-keys||skip-disable-keys||Do not disable keys|
|--skip-extended-insert||skip-extended-insert||Turn off extended-insert|
|--skip-opt||skip-opt||Turn off the options set by --opt|
|--skip-quick||skip-quick||Do not retrieve rows for a table from the server a row at a time|
|--skip-quote-names||skip-quote-names||Do not quote identifiers|
|--skip-set-charset||skip-set-charset||Suppress the SET NAMES statement|
|--skip-triggers||skip-triggers||Do not dump triggers|
|--skip-tz-utc||skip-tz-utc||Turn off tz-utc|
|--ssl-ca=file_name||ssl-ca||The path to a file that contains a list of trusted SSL CAs|
|--ssl-capath=dir_name||ssl-capath||The path to a directory that contains trusted SSL CA certificates in PEM format|
|--ssl-cert=file_name||ssl-cert||The name of the SSL certificate file to use for establishing a secure connection|
|--ssl-cipher=cipher_list||ssl-cipher||A list of allowable ciphers to use for SSL encryption|
|--ssl-crl=file_name||ssl-crl||The path to a file that contains certificate revocation lists|
|--ssl-crlpath=dir_name||ssl-crlpath||The path to a directory that contains certificate revocation list files|
|--ssl-key=file_name||ssl-key||The name of the SSL key file to use for establishing a secure connection|
|--ssl-verify-server-cert||ssl-verify-server-cert||The server's Common Name value in its certificate is verified against the host name used when connecting to the server|
|--tab=path||tab||Produce tab-separated data files|
|--tables||tables||Override the --databases or -B option|
|--triggers||triggers||Dump triggers for each dumped table|
|--tz-utc||tz-utc||Add SET TIME_ZONE='+00:00' to the dump file|
|--user=user_name||user||MySQL user name to use when connecting to server|
|--version||Display version information and exit|
|--where='where_condition'||where||Dump only rows selected by the given WHERE condition|
|--xml||xml||Produce XML output|
The mysqldump command logs into a MySQL server to extract information. The following options specify how to connect to the MySQL server, either on the same machine or a remote system.
On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server.
Compress all information sent between the client and the server if both support compression.
The client-side authentication plugin to use. See Section 6.3.7, "Pluggable Authentication".
Dump data from the MySQL server on the given host. The default host is
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
-p option on the command line, mysqldump prompts for one.
Specifying a password on the command line should be considered insecure. See Section 18.104.22.168, "End-User Guidelines for Password Security". You can use an option file to avoid giving the password on the command line.
On Windows, connect to the server using a named pipe. This option applies only if the server supports named-pipe connections.
The directory in which to look for plugins. It may be necessary to specify this option if the
option is used to specify an authentication plugin but mysqldump does not find it. See Section
6.3.7, "Pluggable Authentication".
The TCP/IP port number to use for the connection.
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. For details on the permissible values, see Section 4.2.2, "Connecting to the MySQL Server".
For connections to
localhost, the Unix socket file to use, or, on
Windows, the name of the named pipe to use.
The MySQL user name to use when connecting to the server.
You can also set the following variables by using
The maximum size of the buffer for client/server communication. The maximum is 1GB.
The initial size of the buffer for client/server communication. When creating multiple-row
statements (as with the
--opt option), mysqldump creates rows up to
net_buffer_length length. If you increase this variable, ensure
net_buffer_length variable in the MySQL server is at least this
Usage scenarios for mysqldump include setting up an entire new MySQL instance (including database tables), and replacing data inside an existing instance with existing databases and tables. The following options let you specify which things to tear down and set up when restoring a dump, by encoding various DDL statements within the dump file.
statement before each
DATABASE statement. This option is typically used in conjunction with the
--databases option because no
CREATE DATABASE statements are written unless one of those
options is specified.
Adds to a table dump all SQL statements needed to create any tablespaces used by an
Do not write
statements that re-create each dumped table.
The following options print debugging information, encode debugging information in the dump file, or let the dump operation proceed regardless of potential problems.
Permit creation of column names that are keywords. This works by prefixing each column name with the table name.
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
Write a debugging log. A typical
debug_options string is
default value is
Print some debugging information when the program exits.
Print debugging information and memory and CPU usage statistics when the program exits.
-- Dump completed on
However, the date causes dump files taken at different times to appear to be different, even if the
data are otherwise identical.
--skip-dump-date control whether the date is added to the comment.
The default is
(include the date in the comment).
--skip-dump-date suppresses date printing.
Ignore all errors; continue even if an SQL error occurs during a table dump.
One use for this option is to cause mysqldump to continue executing even when it
encounters a view that has become invalid because the definition refers to a table that has been
--force, mysqldump exits with an error message. With
--force, mysqldump prints the error message, but it also
writes an SQL comment containing the view definition to the dump output and continues executing.
Log warnings and errors by appending them to the named file. The default is to do no logging.
See the description for the
Verbose mode. Print more information about what the program does.
The following options display information about the mysqldump command itself.
The following options change how the mysqldump command represents character data with national language settings.
The directory where character sets are installed. See Section 10.5, "Character Set Configuration".
Turns off the
--set-charset setting, the same as specifying
to the output. This option is enabled by default. To suppress the
NAMES statement, use
The mysqldump command is frequently used to create an empty instance, or an instance including data, on a slave server in a replication configuration. The following options apply to dumping and restoring data on replication master and slave servers.
This option is similar to
--master-data except that it is used to dump a replication slave
server to produce a dump file that can be used to set up another server as a slave that has the same
master as the dumped server. 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 slave's master (rather than the coordinates of
the dumped server, as is done by the
--master-data option). These are the master server coordinates
from which the slave should start replicating.
The option value is handled the same way as for
--master-data and has the same effect as
in terms of enabling or disabling other options and in how locking is handled.
This option causes mysqldump to stop the slave SQL thread before the dump and restart it again after.
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
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
privilege and the binary log must be enabled.
--master-data option automatically turns off
--lock-tables. It also turns on
--single-transaction also is specified, in which case, a global read
lock is acquired only for a short time at the beginning of the dump (see the description for
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, using the
This option enables control over global transaction ID (GTID) information written to the dump file,
by indicating whether to add a
@@global.gtid_purged statement to the output.
The following table shows the permitted option values. The default value is
The following options specify how to represent the entire dump file or certain kinds of data in the dump file. They also control whether certain optional information is written to the dump file.
Produce output that is more compatible with other database systems or with older MySQL servers. The
name can be
use several values, separate them by commas. These values have the same meaning as the corresponding
options for setting the server SQL mode. See Section 5.1.7,
"Server SQL Modes".
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.
This option requires a server version of 4.1.0 or higher. With older servers, it does nothing.
INSERT statements that include column names.
Include all MySQL-specific table options in the
CREATE TABLE statements.
Quote identifiers (such as database, table, and column names) within "
`" characters. If the
ANSI_QUOTES SQL mode is enabled, identifiers are quoted within "
This option is enabled by default. It can be disabled with
--skip-quote-names, but this option should be given after any option
that may enable
Direct output to a given file. This option should be used on Windows to prevent newline "
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
Produce tab-separated text-format data files. For each dumped table, mysqldump creates a
file that contains the
CREATE TABLE statement that creates the table, and the server writes
contains its data. The option value is the directory in which to write the files.
This option should be used only when mysqldump is run on the same machine as the mysqld 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
Column values are converted to the character set specified by the
This option enables
TIMESTAMP columns to be dumped and reloaded between servers in
different time zones. mysqldump
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
Write dump output as well-formed XML.
and Empty Values: For a column named
an empty string, and the string value
'NULL' are distinguished from one
another in the output generated by this option as follows.
XML output from mysqldump includes the XML namespace, as shown here:
mysqldump --xml -u root world City<?xml version="1.0"?><mysqldump 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></mysqldump>
The following options control which kinds of schema objects are written to the dump file: by category, such as
triggers or events; by name, for example, choosing which databases and tables to dump; or even filtering rows
from the table data using a
Dump all tables in all databases. This is the same as using the
--databases option and naming all the databases on the command line.
Dump several databases. Normally, mysqldump 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.
statements are included in the output before each new database.
Include Event Scheduler events for the dumped databases in the output.
Ignore the specified errors. The option value is a comma-separated list of error numbers specifying
the errors to ignore during mysqldump execution. If the
--force option is also given to ignore all errors,
--force takes precedence.
This option was added in MySQL 5.7.1.
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.
Do not write any table row information (that is, do not dump table contents). This is useful if you
want to dump only the
TABLE statement for the table (for example, to create an empty copy of the table by
loading the dump file).
Include stored routines (procedures and functions) for the dumped databases in the output. Use of
this option requires the
privilege for the
mysql.proc table. The output generated by using
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 MySQL account that has appropriate
privileges for the
Include triggers for each dumped table in the output. This option is enabled by default; disable it
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
The following options are the most relevant for the performance particularly of the restore operations. For
large data sets, restore operation (processing the
INSERT statements in the dump
file) is the most time-consuming part. When it is urgent to restore data quickly, plan and test the performance
of this stage in advance. For restore times measured in hours, you might prefer an alternative backup and
restore solution, such as
and mixed-use databases, or mysqlhotcopy for
Performance is also affected by the transactional options, primarily for the dump operation.
For each table, surround the
INSERT statements with
/*!40000 ALTER TABLE and
tbl_name DISABLE KEYS */;
/*!40000 ALTER TABLE 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
INSERT syntax that include several
VALUES lists. This results in a smaller dump file and speeds up inserts
when the file is reloaded.
This option, enabled by default, is shorthand for the combination of
--set-charset. It gives a fast dump operation and produces a dump file
that can be reloaded into a MySQL server quickly.
--opt option is enabled by default, you only specify its
to turn off several default settings. See the discussion of
mysqldump option groups for information about selectively
enabling or disabling a subset of the options affected by
This option is useful for dumping large tables. It forces mysqldump 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.
See the description for the
The following options trade off the performance of the dump operation, against the reliability and consistency of the exported data.
Flush the MySQL server log files before starting the dump. This option requires the
RELOAD privilege. If you use this option in combination with the
option, the logs are flushed for each database dumped. The
exception is when using
--single-transaction: 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 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.
For each dumped database, lock all tables to be dumped before dumping them. The tables are locked
READ LOCAL to permit concurrent inserts in the case of
MyISAM 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.
--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.
Some options, such as
--opt, automatically enable
If you want to override this, use
--skip-lock-tables at the end of the
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 makes the dump operation take considerably longer.
This option sets the transaction isolation mode to
REPEATABLE READ and
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
START TRANSACTION was issued without blocking any applications.
When using this option, you should keep in mind that only
are dumped in a consistent state. For example, any
MEMORY tables dumped while using this option may still change state.
To dump large tables, combine the
--single-transaction option with the
option turns on several settings that work together to perform a fast dump operation. All of these
settings are on by default, because
--opt is on by default. Thus you rarely
if ever specify
--opt. Instead, you can turn these settings off as a group
--skip-opt, the optionally re-enable certain settings by
specifying the associated options later on the command line.
--compact option turns off several settings that control whether optional
statements and comments appear in the output. Again, you can follow this option with other options that
re-enable certain settings, or turn all the settings on by using the
When you selectively enable or disable the effect of a group option, order is important because options are
processed first to last. For example,
--skip-opt would not have the intended effect; it is the same as
To make a backup of an entire database:
To load the dump file back into the server:
Another way to reload the dump file:
mysql -e "source
mysqldump is also very useful for populating databases by copying data from one MySQL server to another:
db_name| mysql --host=
You can dump several databases with one command:
db_name2...] > my_databases.sql
To dump all databases, use the
mysqldump --all-databases > all_databases.sql
InnoDB tables, mysqldump provides a way of making an online backup:
mysqldump --all-databases --single-transaction > all_databases.sql
This backup acquires a global read lock on all tables (using
FLUSH 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 MySQL 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 MySQL 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 binary log (see Section 5.2.4, "The Binary Log") or at least know the binary log coordinates to which the dump corresponds:
mysqldump --all-databases --master-data=2 > all_databases.sql
mysqldump --all-databases --flush-logs --master-data=2
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 using the
For more information on making backups, see Section 7.2, "Database Backup Methods", and Section 7.3, "Example Backup and Recovery Strategy".
To select the effect of
--opt except for some features, use the
option for each feature. To disable extended inserts and memory buffering, use
--skip-quick is sufficient because
--opt is on by default.)
It is not recommended to restore from a dump made using mysqldump to a MySQL 5.6.9 or earlier server that has GTIDs enabled. See Section 22.214.171.124, "Restrictions on Replication with GTIDs".
mysqldump never dumps the
mysqldump includes statements to recreate the
slow_query_log tables for dumps of the
mysql database. Log table contents are not dumped.
If you encounter problems backing up views due to insufficient privileges, see Section D.5, "Restrictions on Views" for a workaround.