<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="clone-plugin">
      </a>
      7.6.7 The Clone Plugin
     </h3>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="clone-plugin-installation.html">
       7.6.7.1 Installing the Clone Plugin
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-local.html">
       7.6.7.2 Cloning Data Locally
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-remote.html">
       7.6.7.3 Cloning Remote Data
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-concurrent-ddl.html">
       7.6.7.4 Cloning and Concurrent DDL
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-encrypted-data.html">
       7.6.7.5 Cloning Encrypted Data
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-compressed-data.html">
       7.6.7.6 Cloning Compressed Data
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-replication.html">
       7.6.7.7 Cloning for Replication
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-directories.html">
       7.6.7.8 Directories and Files Created During a Cloning Operation
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-failure-handling.html">
       7.6.7.9 Remote Cloning Operation Failure Handling
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-monitoring.html">
       7.6.7.10 Monitoring Cloning Operations
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-stop.html">
       7.6.7.11 Stopping a Cloning Operation
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-option-variable-reference.html">
       7.6.7.12 Clone System Variable Reference
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-options-variables.html">
       7.6.7.13 Clone System Variables
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="clone-plugin-limitations.html">
       7.6.7.14 Clone Plugin Limitations
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <a class="indexterm" name="idm46045255743680">
  </a>
  <a class="indexterm" name="idm46045255742608">
  </a>
  <a class="indexterm" name="idm46045255741536">
  </a>
  <p>
   The clone plugin permits cloning data locally or from a remote
      MySQL server instance. Cloned data is a physical snapshot of data
      stored in
   <code class="literal">
    InnoDB
   </code>
   that includes schemas, tables,
      tablespaces, and data dictionary metadata. The cloned data
      comprises a fully functional data directory, which permits using
      the clone plugin for MySQL server provisioning.
  </p>
  <div class="figure">
   <a name="clone-plugin-local-diagram">
   </a>
   <p class="title">
    <b>
     Figure 7.1 Local Cloning Operation
    </b>
   </p>
   <div class="figure-contents">
    <div class="mediaobject">
     <img alt="The CLONE LOCAL statement clones the data directory on a local MySQL Server instance to another local directory, which is referred to as the clone directory." src="images/clone-local.png" style="width: 100%; max-width: 307px;"/>
    </div>
   </div>
  </div>
  <br class="figure-break"/>
  <p>
   A local cloning operation clones data from the MySQL server
      instance where the cloning operation is initiated to a directory
      on the same server or node where MySQL server instance runs.
  </p>
  <div class="figure">
   <a name="clone-plugin-remote-diagram">
   </a>
   <p class="title">
    <b>
     Figure 7.2 Remote Cloning Operation
    </b>
   </p>
   <div class="figure-contents">
    <div class="mediaobject">
     <img alt="The CLONE INSTANCE statement issued from the local recipient MySQL Server instance clones the data directory from the remote donor MySQL server instance to the data directory on the local recipient MySQL Server instance." src="images/clone-remote.png" style="width: 100%; max-width: 307px;"/>
    </div>
   </div>
  </div>
  <br class="figure-break"/>
  <p>
   A remote cloning operation involves a local MySQL server instance
      (the
   <span class="quote">
    “
    <span class="quote">
     recipient
    </span>
    ”
   </span>
   ) where the cloning operation is
      initiated, and a remote MySQL server instance (the
   <span class="quote">
    “
    <span class="quote">
     donor
    </span>
    ”
   </span>
   ) where the source data is located. When a
      remote cloning operation is initiated on the recipient, cloned
      data is transferred over the network from the donor to the
      recipient. By default, a remote cloning operation removes existing
      user-created data (schemas, tables, tablespaces) and binary logs
      from the recipient data directory before cloning data from the
      donor. Optionally, you can clone data to a different directory on
      the recipient to avoid removing data from the current recipient
      data directory.
  </p>
  <p>
   There is no difference with respect to data that is cloned by a
      local cloning operation as compared to a remote cloning operation.
      Both operations clone the same set of data.
  </p>
  <p>
   The clone plugin supports replication. In addition to cloning
      data, a cloning operation extracts and transfers replication
      coordinates from the donor and applies them on the recipient,
      which enables using the clone plugin for provisioning Group
      Replication members and replicas. Using the clone plugin for
      provisioning is considerably faster and more efficient than
      replicating a large number of transactions (see
   <a class="xref" href="clone-plugin-replication.html" title="7.6.7.7 Cloning for Replication">
    Section 7.6.7.7, “Cloning for Replication”
   </a>
   ). Group Replication
      members can also be configured to use the clone plugin as an
      alternative method of recovery, so that members automatically
      choose the most efficient way to retrieve group data from seed
      members. For more information, see
   <a class="xref" href="group-replication-cloning.html" title="20.5.4.2 Cloning for Distributed Recovery">
    Section 20.5.4.2, “Cloning for Distributed Recovery”
   </a>
   .
  </p>
  <p>
   The clone plugin supports cloning of encrypted and page-compressed
      data. See
   <a class="xref" href="clone-plugin-encrypted-data.html" title="7.6.7.5 Cloning Encrypted Data">
    Section 7.6.7.5, “Cloning Encrypted Data”
   </a>
   , and
   <a class="xref" href="clone-plugin-compressed-data.html" title="7.6.7.6 Cloning Compressed Data">
    Section 7.6.7.6, “Cloning Compressed Data”
   </a>
   .
  </p>
  <p>
   The clone plugin must be installed before you can use it. For
      installation instructions, see
   <a class="xref" href="clone-plugin-installation.html" title="7.6.7.1 Installing the Clone Plugin">
    Section 7.6.7.1, “Installing the Clone Plugin”
   </a>
   . For cloning
      instructions, see
   <a class="xref" href="clone-plugin-local.html" title="7.6.7.2 Cloning Data Locally">
    Section 7.6.7.2, “Cloning Data Locally”
   </a>
   , and
   <a class="xref" href="clone-plugin-remote.html" title="7.6.7.3 Cloning Remote Data">
    Section 7.6.7.3, “Cloning Remote Data”
   </a>
   .
  </p>
  <p>
   Performance Schema tables and instrumentation are provided for
      monitoring cloning operations. See
   <a class="xref" href="clone-plugin-monitoring.html" title="7.6.7.10 Monitoring Cloning Operations">
    Section 7.6.7.10, “Monitoring Cloning Operations”
   </a>
   .
  </p>
 </div>
 <br/>
</div>
