Logical State Snapshot

There is one back-end method available for a Logical State Snapshots: mysqldump.

The Logical State Transfer Method has the following advantages:

  • These transfers are available on live servers. In fact, only a fully initialized server can receive a Logical State Snapshot.

  • These transfers do not require the receptor node to have the same configuration as the Donor Node. This allows you to upgrade storage engine options.

    For example, when using this transfer method you can migrate from the Antelope to the Barracuda file format, use compression resize, or move iblog* files from one partition into another.

The Logical State Transfer Method has the following disadvantages:

  • These transfers are as slow as mysqldump.
  • These transfers require that you configure the receiving database server to accept root connections from potential donor nodes.
  • The receiving server must have a non-corrupted database.


The main advantage of mysqldump is that you can transfer a state snapshot to a working server. That is, you start the server standalone and then instruct it to join a cluster from within the database client command line. You can also use it to migrate from an older database format to a newer one.

mysqldump requires that the receiving node have a fully functional database, which can be empty. It also requires the same root credentials as the donor and root access from the other nodes.

This transfer method is several times slower than the others on sizable databases, but it may prove faster in cases of very small databases. For instance, on a database that is smaller than the log files.


This transfer method is sensitive to the version of mysqldump each node uses. It is not uncommon for a given cluster to have installed several versions. A State Snapshot Transfer can fail if the version one node uses is older and incompatible with the newer server.

On occasion, mysqldump is the only option available. For instance, if you upgrade from a cluster using MySQL 5.1 with the built-in InnoDB support to MySQL 5.5, which uses the InnoDB plugin.

The mysqldump script only runs on the sending node. The output from the script gets piped to the MySQL client that connects to the Joiner Node.

Because mysqldump interfaces through the database client, configuring it requires several steps beyond setting the wsrep_sst_method parameter. For more information on its configuration, see:

For more information on mysqldump, see mysqldump Documentation.