<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="mysql-cluster-programs-ndb-restore">
      </a>
      25.5.23 ndb_restore — Restore an NDB Cluster Backup
     </h3>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045099817888">
  </a>
  <a class="indexterm" name="idm46045099816528">
  </a>
  <a class="indexterm" name="idm46045099815168">
  </a>
  <a class="indexterm" name="idm46045099813808">
  </a>
  <a class="indexterm" name="idm46045099812448">
  </a>
  <p>
   The NDB Cluster restoration program is implemented as a separate
        command-line utility
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   , which can
        normally be found in the MySQL
   <code class="filename">
    bin
   </code>
   directory. This program reads the files created as a result of
        the backup and inserts the stored information into the database.
  </p>
  <p>
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   must be executed once for each of
        the backup files that were created by the
   <a class="link" href="mysql-cluster-backup-using-management-client.html" title="25.6.8.2 Using The NDB Cluster Management Client to Create a Backup">
    <code class="literal">
     START BACKUP
    </code>
   </a>
   command used to
        create the backup (see
   <a class="xref" href="mysql-cluster-backup-using-management-client.html" title="25.6.8.2 Using The NDB Cluster Management Client to Create a Backup">
    Section 25.6.8.2, “Using The NDB Cluster Management Client to Create a Backup”
   </a>
   ).
        This is equal to the number of data nodes in the cluster at the
        time that the backup was created.
  </p>
  <a class="indexterm" name="idm46045099804832">
  </a>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    Before using
    <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
     <span class="command">
      <strong>
       ndb_restore
      </strong>
     </span>
    </a>
    , it is recommended
          that the cluster be running in single user mode, unless you
          are restoring multiple data nodes in parallel. See
    <a class="xref" href="mysql-cluster-single-user-mode.html" title="25.6.6 NDB Cluster Single User Mode">
     Section 25.6.6, “NDB Cluster Single User Mode”
    </a>
    , for more
          information.
   </p>
  </div>
  <p>
   Options that can be used with
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   are
        shown in the following table. Additional descriptions follow the
        table.
  </p>
  <p>
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_allow-pk-changes">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_allow-pk-changes">
       <code class="option">
        --allow-pk-changes
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099795456">
     </a>
     <a class="indexterm" name="idm46045099793968">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for allow-pk-changes">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --allow-pk-changes[=0|1]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When this option is set to
      <code class="literal">
       1
      </code>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      allows the primary keys in a
            table definition to differ from that of the same table in
            the backup. This may be desirable when backing up and
            restoring between different schema versions with primary key
            changes on one or more tables, and it appears that
            performing the restore operation using ndb_restore is
            simpler or more efficient than issuing many
      <a class="link" href="alter-table.html" title="15.1.9 ALTER TABLE Statement">
       <code class="literal">
        ALTER TABLE
       </code>
      </a>
      statements after
            restoring table schemas and data.
     </p>
     <p>
      The following changes in primary key definitions are
            supported by
      <code class="option">
       --allow-pk-changes
      </code>
      :
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <span class="bold">
          <strong>
           Extending the primary
                key
          </strong>
         </span>
         : A non-nullable column that exists in the
                table schema in the backup becomes part of the
                table's primary key in the database.
        </p>
        <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
         <div class="admon-title">
          Important
         </div>
         <p>
          When extending a table's primary key, any columns
                  which become part of primary key must not be updated
                  while the backup is being taken; any such updates
                  discovered by
          <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
           <span class="command">
            <strong>
             ndb_restore
            </strong>
           </span>
          </a>
          cause the
                  restore operation to fail, even when no change in
                  value takes place. In some cases, it may be possible
                  to override this behavior using the
          <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ignore-extended-pk-updates">
           <code class="option">
            --ignore-extended-pk-updates
           </code>
          </a>
          option; see the description of this option for more
                  information.
         </p>
        </div>
       </li>
       <li class="listitem">
        <p>
         <span class="bold">
          <strong>
           Contracting the primary key
                (1)
          </strong>
         </span>
         : A column that is already part of the
                table's primary key in the backup schema is no
                longer part of the primary key, but remains in the
                table.
        </p>
       </li>
       <li class="listitem">
        <p>
         <span class="bold">
          <strong>
           Contracting the primary key
                (2)
          </strong>
         </span>
         : A column that is already part of the
                table's primary key in the backup schema is removed
                from the table entirely.
        </p>
       </li>
      </ul>
     </div>
     <p>
      These differences can be combined with other schema
            differences supported by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      ,
            including changes to blob and text columns requiring the use
            of staging tables.
     </p>
     <p>
      Basic steps in a typical scenario using primary key schema
            changes are listed here:
     </p>
     <div class="orderedlist">
      <ol class="orderedlist" type="1">
       <li class="listitem">
        <p>
         Restore table schemas using
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-meta">
          <code class="option">
           --restore-meta
          </code>
         </a>
        </p>
       </li>
       <li class="listitem">
        <p>
         Alter schema to that desired, or create it
        </p>
       </li>
       <li class="listitem">
        <p>
         Back up the desired schema
        </p>
       </li>
       <li class="listitem">
        <p>
         Run
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_disable-indexes">
          <code class="option">
           --disable-indexes
          </code>
         </a>
         using the backup from the previous step, to drop indexes
                and constraints
        </p>
       </li>
       <li class="listitem">
        <p>
         Run
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_allow-pk-changes">
          <code class="option">
           --allow-pk-changes
          </code>
         </a>
         (possibly along with
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ignore-extended-pk-updates">
          <code class="option">
           --ignore-extended-pk-updates
          </code>
         </a>
         ,
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_disable-indexes">
          <code class="option">
           --disable-indexes
          </code>
         </a>
         ,
                and possibly other options as needed) to restore all
                data
        </p>
       </li>
       <li class="listitem">
        <p>
         Run
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rebuild-indexes">
          <code class="option">
           --rebuild-indexes
          </code>
         </a>
         using the backup made with the desired schema, to
                rebuild indexes and constraints
        </p>
       </li>
      </ol>
     </div>
     <p>
      When extending the primary key, it may be necessary for
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to use a temporary secondary
            unique index during the restore operation to map from the
            old primary key to the new one. Such an index is created
            only when necessary to apply events from the backup log to a
            table which has an extended primary key. This index is named
      <code class="literal">
       NDB$RESTORE_PK_MAPPING
      </code>
      , and is created on
            each table requiring it; it can be shared, if necessary, by
            multiple instances of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      instances running in parallel. (Running
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rebuild-indexes">
       <code class="option">
        --rebuild-indexes
       </code>
      </a>
      at the
            end of the restore process causes this index to be dropped.)
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_append">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_append">
       <code class="option">
        --append
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099734816">
     </a>
     <a class="indexterm" name="idm46045099733328">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for append">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --append
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When used with the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_tab">
       <code class="option">
        --tab
       </code>
      </a>
      and
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-data">
       <code class="option">
        --print-data
       </code>
      </a>
      options, this causes the data to be appended to any existing
            files having the same names.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_backup-path">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-path">
       <code class="option">
        --backup-path
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        dir_name
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099720880">
     </a>
     <a class="indexterm" name="idm46045099719392">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for backup-path">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --backup-path=path
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Directory name
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           ./
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      The path to the backup directory is required; this is
            supplied to
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      using the
      <code class="option">
       --backup-path
      </code>
      option, and must include the
            subdirectory corresponding to the ID backup of the backup to
            be restored. For example, if the data node's
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-datadir">
       <code class="literal">
        DataDir
       </code>
      </a>
      is
      <code class="filename">
       /var/lib/mysql-cluster
      </code>
      , then the backup
            directory is
      <code class="filename">
       /var/lib/mysql-cluster/BACKUP
      </code>
      , and the
            backup files for the backup with the ID 3 can be found in
      <code class="filename">
       /var/lib/mysql-cluster/BACKUP/BACKUP-3
      </code>
      .
            The path may be absolute or relative to the directory in
            which the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      executable is
            located, and may be optionally prefixed with
      <code class="option">
       backup-path=
      </code>
      .
     </p>
     <p>
      It is possible to restore a backup to a database with a
            different configuration than it was created from. For
            example, suppose that a backup with backup ID
      <code class="literal">
       12
      </code>
      , created in a cluster with two storage
            nodes having the node IDs
      <code class="literal">
       2
      </code>
      and
      <code class="literal">
       3
      </code>
      , is to be restored to a cluster with
            four nodes. Then
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      must be run
            twice—once for each storage node in the cluster where
            the backup was taken. However,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      cannot always restore backups
            made from a cluster running one version of MySQL to a
            cluster running a different MySQL version. See
      <a class="xref" href="mysql-cluster-upgrade-downgrade.html" title="25.3.7 Upgrading and Downgrading NDB Cluster">
       Section 25.3.7, “Upgrading and Downgrading NDB Cluster”
      </a>
      , for more
            information.
     </p>
     <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Important
      </div>
      <p>
       It is not possible to restore a backup made from a newer
              version of NDB Cluster using an older version of
       <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
        <span class="command">
         <strong>
          ndb_restore
         </strong>
        </span>
       </a>
       . You can restore a backup
              made from a newer version of MySQL to an older cluster,
              but you must use a copy of
       <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
        <span class="command">
         <strong>
          ndb_restore
         </strong>
        </span>
       </a>
       from the newer NDB Cluster version to do so.
      </p>
      <p>
       For example, to restore a cluster backup taken from a
              cluster running NDB Cluster 8.4.0 to a
              cluster running NDB Cluster 8.0.41, you
              must use the
       <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
        <span class="command">
         <strong>
          ndb_restore
         </strong>
        </span>
       </a>
       that comes
              with the NDB Cluster 8.0.41
              distribution.
      </p>
     </div>
     <p>
      For more rapid restoration, the data may be restored in
            parallel, provided that there is a sufficient number of
            cluster connections available. That is, when restoring to
            multiple nodes in parallel, you must have an
      <code class="literal">
       [api]
      </code>
      or
      <code class="literal">
       [mysqld]
      </code>
      section in the cluster
      <code class="filename">
       config.ini
      </code>
      file
            available for each concurrent
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      process. However, the data files must always be applied
            before the logs.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_backup-password">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password">
       <code class="option">
        --backup-password=
        <em class="replaceable">
         <code>
          password
         </code>
        </em>
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099680560">
     </a>
     <a class="indexterm" name="idm46045099679072">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for backup-password">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --backup-password=password
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option specifies a password to be used when decrypting
            an encrypted backup with the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_decrypt">
       <code class="option">
        --decrypt
       </code>
      </a>
      option. This
            must be the same password that was used to encrypt the
            backup.
     </p>
     <p>
      The password must be 1 to 256 characters in length, and must
            be enclosed by single or double quotation marks. It can
            contain any of the ASCII characters having character codes
            32, 35, 38, 40-91, 93, 95, and 97-126; in other words, it
            can use any printable ASCII characters except for
      <code class="literal">
       !
      </code>
      ,
      <code class="literal">
       '
      </code>
      ,
      <code class="literal">
       "
      </code>
      ,
      <code class="literal">
       $
      </code>
      ,
      <code class="literal">
       %
      </code>
      ,
      <code class="literal">
       \
      </code>
      , and
      <code class="literal">
       ^
      </code>
      .
     </p>
     <p>
      It is possible to omit the password, in which case
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      waits for it to be supplied
            from
      <code class="literal">
       stdin
      </code>
      , as when using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password-from-stdin">
       <code class="option">
        --backup-password-from-stdin
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_backup-password-from-stdin">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password-from-stdin">
       <code class="option">
        --backup-password-from-stdin[=TRUE|FALSE]
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099654432">
     </a>
     <a class="indexterm" name="idm46045099652928">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for backup-password-from-stdin">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --backup-password-from-stdin
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When used in place of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password">
       <code class="option">
        --backup-password
       </code>
      </a>
      , this
            option enables input of the backup password from the system
            shell (
      <code class="literal">
       stdin
      </code>
      ), similar to how this is
            done when supplying the password interactively to
      <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
       <span class="command">
        <strong>
         mysql
        </strong>
       </span>
      </a>
      when using the
      <a class="link" href="mysql-command-options.html#option_mysql_password">
       <code class="option">
        --password
       </code>
      </a>
      without supplying
            the password on the command line.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_backupid">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid">
       <code class="option">
        --backupid
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
      ,
      <code class="option">
       -b
      </code>
     </p>
     <a class="indexterm" name="idm46045099638128">
     </a>
     <a class="indexterm" name="idm46045099636640">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for backupid">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --backupid=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           none
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option is required; it is used to specify the ID or
            sequence number of the backup, and is the same number shown
            by the management client in the
      <code class="literal">
       Backup
       <em class="replaceable">
        <code>
         backup_id
        </code>
       </em>
       completed
      </code>
      message displayed upon completion of a backup. (See
      <a class="xref" href="mysql-cluster-backup-using-management-client.html" title="25.6.8.2 Using The NDB Cluster Management Client to Create a Backup">
       Section 25.6.8.2, “Using The NDB Cluster Management Client to Create a Backup”
      </a>
      .)
     </p>
     <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Important
      </div>
      <p>
       When restoring cluster backups, you must be sure to
              restore all data nodes from backups having the same backup
              ID. Using files from different backups results at best in
              restoring the cluster to an inconsistent state, and is
              likely to fail altogether.
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_character-sets-dir">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_character-sets-dir">
       <code class="option">
        --character-sets-dir
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099619168">
     </a>
     <a class="indexterm" name="idm46045099617712">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for character-sets-dir">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --character-sets-dir=path
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Directory containing character sets.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_connect">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_connect">
       <code class="option">
        --connect
       </code>
      </a>
      ,
      <code class="option">
       -c
      </code>
     </p>
     <a class="indexterm" name="idm46045099607440">
     </a>
     <a class="indexterm" name="idm46045099605952">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for connect">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --connect=connection_string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           localhost:1186
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Alias for
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-connectstring">
       <code class="option">
        --ndb-connectstring
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_connect-retries">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_connect-retries">
       <code class="option">
        --connect-retries
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099590672">
     </a>
     <a class="indexterm" name="idm46045099589184">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for connect-retries">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --connect-retries=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           12
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           12
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Number of times to retry connection before giving up.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_connect-retry-delay">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_connect-retry-delay">
       <code class="option">
        --connect-retry-delay
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099570160">
     </a>
     <a class="indexterm" name="idm46045099568704">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for connect-retry-delay">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --connect-retry-delay=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           5
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           5
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Number of seconds to wait between attempts to contact
            management server.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_connect-string">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_connect-string">
       <code class="option">
        --connect-string
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099549456">
     </a>
     <a class="indexterm" name="idm46045099547968">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for connect-string">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --connect-string=connection_string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Same as
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-connectstring">
       <code class="option">
        --ndb-connectstring
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_core-file">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_core-file">
       <code class="option">
        --core-file
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099532656">
     </a>
     <a class="indexterm" name="idm46045099531168">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for core-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --core-file
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Write core file on error; used in debugging.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_decrypt">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_decrypt">
       <code class="option">
        --decrypt
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099521504">
     </a>
     <a class="indexterm" name="idm46045099520016">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for decrypt">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --decrypt
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Decrypt an encrypted backup using the password supplied by
            the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password">
       <code class="option">
        --backup-password
       </code>
      </a>
      option.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_defaults-extra-file">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_defaults-extra-file">
       <code class="option">
        --defaults-extra-file
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099509280">
     </a>
     <a class="indexterm" name="idm46045099507824">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-extra-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-extra-file=path
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Read given file after global files are read.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_defaults-file">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_defaults-file">
       <code class="option">
        --defaults-file
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099493472">
     </a>
     <a class="indexterm" name="idm46045099491984">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-file=path
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Read default options from given file only.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_defaults-group-suffix">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_defaults-group-suffix">
       <code class="option">
        --defaults-group-suffix
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099477696">
     </a>
     <a class="indexterm" name="idm46045099476192">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-group-suffix">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-group-suffix=string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Also read groups with concat(group, suffix).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_disable-indexes">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_disable-indexes">
       <code class="option">
        --disable-indexes
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099462080">
     </a>
     <a class="indexterm" name="idm46045099460592">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for disable-indexes">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --disable-indexes
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Disable restoration of indexes during restoration of the
            data from a native
      <code class="literal">
       NDB
      </code>
      backup.
            Afterwards, you can restore indexes for all tables at once
            with multithreaded building of indexes using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rebuild-indexes">
       <code class="option">
        --rebuild-indexes
       </code>
      </a>
      , which
            should be faster than rebuilding indexes concurrently for
            very large tables.
     </p>
     <p>
      This option also drops any foreign keys specified in the
            backup.
     </p>
     <p>
      MySQL can open an
      <code class="literal">
       NDB
      </code>
      table for which one
            or more indexes cannot be found, provided the query does not
            use any of the affected indexes; otherwise the query is
            rejected with
      <a class="ulink" href="/doc/mysql-errors/8.4/en/server-error-reference.html#error_er_not_keyfile" target="_top">
       <code class="literal">
        ER_NOT_KEYFILE
       </code>
      </a>
      . In the
            latter case, you can temporarily work around the problem by
            executing an
      <a class="link" href="alter-table.html" title="15.1.9 ALTER TABLE Statement">
       <code class="literal">
        ALTER TABLE
       </code>
      </a>
      statement such as this one:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-sql"><div class="docs-select-all right" id="sa873374"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">ALTER</span> <span class="token keyword">TABLE</span> tbl <span class="token keyword">ALTER</span> <span class="token keyword">INDEX</span> idx <span class="token keyword">INVISIBLE</span><span class="token punctuation">;</span></code></pre>
     </div>
     <p>
      This causes MySQL to ignore the index
      <code class="literal">
       idx
      </code>
      on table
      <code class="literal">
       tbl
      </code>
      . See
      <a class="xref" href="alter-table.html#alter-table-index" title="Primary Keys and Indexes">
       Primary Keys and Indexes
      </a>
      , for more information,
            as well as
      <a class="xref" href="invisible-indexes.html" title="10.3.12 Invisible Indexes">
       Section 10.3.12, “Invisible Indexes”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_dont-ignore-systab-0">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_dont-ignore-systab-0">
       <code class="option">
        --dont-ignore-systab-0
       </code>
      </a>
      ,
      <code class="option">
       -f
      </code>
     </p>
     <a class="indexterm" name="idm46045099440000">
     </a>
     <a class="indexterm" name="idm46045099438544">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for dont-ignore-systab-0">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --dont-ignore-systab-0
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Normally, when restoring table data and metadata,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      ignores the copy of the
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      system table that is
            present in the backup.
      <code class="option">
       --dont-ignore-systab-0
      </code>
      causes the system
            table to be restored.
      <span class="emphasis">
       <em>
        This option is intended for
            experimental and development use only, and is not
            recommended in a production environment
       </em>
      </span>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_exclude-databases">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-databases">
       <code class="option">
        --exclude-databases
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        db-list
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099424752">
     </a>
     <a class="indexterm" name="idm46045099423296">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-databases">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-databases=list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Comma-delimited list of one or more databases which should
            not be restored.
     </p>
     <p>
      This option is often used in combination with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-tables">
       <code class="option">
        --exclude-tables
       </code>
      </a>
      ; see
            that option's description for further information and
            examples.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_exclude-intermediate-sql-tables">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-intermediate-sql-tables">
       <code class="option">
        --exclude-intermediate-sql-tables[
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        TRUE|FALSE]
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099406816">
     </a>
     <a class="indexterm" name="idm46045099405312">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-intermediate-sql-tables">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-intermediate-sql-tables[=TRUE|FALSE]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           TRUE
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When performing copying
      <a class="link" href="alter-table.html" title="15.1.9 ALTER TABLE Statement">
       <code class="literal">
        ALTER
            TABLE
       </code>
      </a>
      operations,
      <a class="link" href="mysqld.html" title="6.3.1 mysqld — The MySQL Server">
       <span class="command">
        <strong>
         mysqld
        </strong>
       </span>
      </a>
      creates intermediate tables (whose names are prefixed with
      <code class="literal">
       #sql-
      </code>
      ). When
      <code class="literal">
       TRUE
      </code>
      , the
      <code class="option">
       --exclude-intermediate-sql-tables
      </code>
      option
            keeps
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      from restoring such
            tables that may have been left over from these operations.
            This option is
      <code class="literal">
       TRUE
      </code>
      by default.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_exclude-missing-columns">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-missing-columns">
       <code class="option">
        --exclude-missing-columns
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099384464">
     </a>
     <a class="indexterm" name="idm46045099382960">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-missing-columns">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-missing-columns
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      It is possible to restore only selected table columns using
            this option, which causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to
            ignore any columns missing from tables being restored as
            compared to the versions of those tables found in the
            backup. This option applies to all tables being restored. If
            you wish to apply this option only to selected tables or
            databases, you can use it in combination with one or more of
            the
      <code class="option">
       --include-*
      </code>
      or
      <code class="option">
       --exclude-*
      </code>
      options described elsewhere in
            this section to do so, then restore data to the remaining
            tables using a complementary set of these options.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_exclude-missing-tables">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-missing-tables">
       <code class="option">
        --exclude-missing-tables
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099370288">
     </a>
     <a class="indexterm" name="idm46045099368784">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-missing-tables">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-missing-tables
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      It is possible to restore only selected tables using this
            option, which causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to
            ignore any tables from the backup that are not found in the
            target database.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_exclude-tables">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-tables">
       <code class="option">
        --exclude-tables
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        table-list
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099357280">
     </a>
     <a class="indexterm" name="idm46045099355792">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-tables">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-tables=list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      List of one or more tables to exclude; each table reference
            must include the database name. Often used together with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-databases">
       <code class="option">
        --exclude-databases
       </code>
      </a>
      .
     </p>
     <p>
      When
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-databases">
       <code class="option">
        --exclude-databases
       </code>
      </a>
      or
      <code class="option">
       --exclude-tables
      </code>
      is used, only those
            databases or tables named by the option are excluded; all
            other databases and tables are restored by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      .
     </p>
     <p>
      This table shows several invocations of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      using
      <code class="option">
       --exclude-*
      </code>
      options (other options possibly
            required have been omitted for clarity), and the effects
            these options have on restoring from an NDB Cluster backup:
     </p>
     <div class="table">
      <a name="idm46045099337280">
      </a>
      <p class="title">
       <b>
        Table 25.23 Several invocations of ndb_restore using --exclude-*
                options, and the effects these options have on restoring from an
NDB Cluster backup.
       </b>
      </p>
      <div class="table-contents">
       <table>
        <colgroup>
         <col style="width: 50%"/>
         <col style="width: 50%"/>
        </colgroup>
        <thead>
         <tr>
          <th>
           Option
          </th>
          <th>
           Result
          </th>
         </tr>
        </thead>
        <tbody>
         <tr>
          <td>
           <code class="option">
            --exclude-databases=db1
           </code>
          </td>
          <td>
           All tables in all databases except
           <code class="literal">
            db1
           </code>
           are restored;
                  no tables in
           <code class="literal">
            db1
           </code>
           are restored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --exclude-databases=db1,db2
           </code>
           (or
           <code class="option">
            --exclude-databases=db1
           </code>
           <code class="option">
            --exclude-databases=db2
           </code>
           )
          </td>
          <td>
           All tables in all databases except
           <code class="literal">
            db1
           </code>
           and
           <code class="literal">
            db2
           </code>
           are restored; no tables in
           <code class="literal">
            db1
           </code>
           or
           <code class="literal">
            db2
           </code>
           are
                  restored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --exclude-tables=db1.t1
           </code>
          </td>
          <td>
           All tables except
           <code class="literal">
            t1
           </code>
           in database
           <code class="literal">
            db1
           </code>
           are restored; all other tables
                  in
           <code class="literal">
            db1
           </code>
           are restored; all tables in
                  all other databases are restored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --exclude-tables=db1.t2,db2.t1
           </code>
           (or
           <code class="option">
            --exclude-tables=db1.t2
           </code>
           <code class="option">
            --exclude-tables=db2.t1)
           </code>
          </td>
          <td>
           All tables in database
           <code class="literal">
            db1
           </code>
           except for
           <code class="literal">
            t2
           </code>
           and all tables in database
           <code class="literal">
            db2
           </code>
           except for table
           <code class="literal">
            t1
           </code>
           are restored; no other tables in
           <code class="literal">
            db1
           </code>
           or
           <code class="literal">
            db2
           </code>
           are
                  restored; all tables in all other databases are
                  restored
          </td>
         </tr>
        </tbody>
       </table>
      </div>
     </div>
     <br class="table-break"/>
     <p>
      You can use these two options together. For example, the
            following causes all tables in all databases
      <span class="emphasis">
       <em>
        except for
       </em>
      </span>
      databases
      <code class="literal">
       db1
      </code>
      and
      <code class="literal">
       db2
      </code>
      , and
            tables
      <code class="literal">
       t1
      </code>
      and
      <code class="literal">
       t2
      </code>
      in
            database
      <code class="literal">
       db3
      </code>
      , to be restored:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa28461299"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token punctuation">[</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">]</span> <span class="token constant">--exclude-databases</span><span class="token attr-value"><span class="token punctuation">=</span>db1,db2</span> <span class="token constant">--exclude-tables</span><span class="token attr-value"><span class="token punctuation">=</span>db3.t1,db3.t2</span></code></pre>
     </div>
     <p>
      (Again, we have omitted other possibly necessary options in
            the interest of clarity and brevity from the example just
            shown.)
     </p>
     <p>
      You can use
      <code class="option">
       --include-*
      </code>
      and
      <code class="option">
       --exclude-*
      </code>
      options together, subject to
            the following rules:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         The actions of all
         <code class="option">
          --include-*
         </code>
         and
         <code class="option">
          --exclude-*
         </code>
         options are cumulative.
        </p>
       </li>
       <li class="listitem">
        <p>
         All
         <code class="option">
          --include-*
         </code>
         and
         <code class="option">
          --exclude-*
         </code>
         options are evaluated in
                the order passed to ndb_restore, from right to left.
        </p>
       </li>
       <li class="listitem">
        <p>
         In the event of conflicting options, the first
                (rightmost) option takes precedence. In other words, the
                first option (going from right to left) that matches
                against a given database or table
         <span class="quote">
          “
          <span class="quote">
           wins
          </span>
          ”
         </span>
         .
        </p>
       </li>
      </ul>
     </div>
     <p>
      For example, the following set of options causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to restore all tables from
            database
      <code class="literal">
       db1
      </code>
      except
      <code class="literal">
       db1.t1
      </code>
      , while restoring no other tables
            from any other databases:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa78362150"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token constant">--include-databases</span><span class="token attr-value"><span class="token punctuation">=</span>db1</span> <span class="token constant">--exclude-tables</span><span class="token attr-value"><span class="token punctuation">=</span>db1.t1</span></code></pre>
     </div>
     <p>
      However, reversing the order of the options just given
            simply causes all tables from database
      <code class="literal">
       db1
      </code>
      to be restored (including
      <code class="literal">
       db1.t1
      </code>
      , but no tables from any other
            database), because the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-databases">
       <code class="option">
        --include-databases
       </code>
      </a>
      option, being farthest to the right, is the first match
            against database
      <code class="literal">
       db1
      </code>
      and thus takes
            precedence over any other option that matches
      <code class="literal">
       db1
      </code>
      or any tables in
      <code class="literal">
       db1
      </code>
      :
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa70520475"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token constant">--exclude-tables</span><span class="token attr-value"><span class="token punctuation">=</span>db1.t1</span> <span class="token constant">--include-databases</span><span class="token attr-value"><span class="token punctuation">=</span>db1</span></code></pre>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_fields-enclosed-by">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-enclosed-by">
       <code class="option">
        --fields-enclosed-by
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        char
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099283104">
     </a>
     <a class="indexterm" name="idm46045099281648">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for fields-enclosed-by">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --fields-enclosed-by=char
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Each column value is enclosed by the string passed to this
            option (regardless of data type; see the description of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-optionally-enclosed-by">
       <code class="option">
        --fields-optionally-enclosed-by
       </code>
      </a>
      ).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_fields-optionally-enclosed-by">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-optionally-enclosed-by">
       <code class="option">
        --fields-optionally-enclosed-by
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099266224">
     </a>
     <a class="indexterm" name="idm46045099264720">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for fields-optionally-enclosed-by">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --fields-optionally-enclosed-by
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      The string passed to this option is used to enclose column
            values containing character data (such as
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        CHAR
       </code>
      </a>
      ,
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        VARCHAR
       </code>
      </a>
      ,
      <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
       <code class="literal">
        BINARY
       </code>
      </a>
      ,
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        TEXT
       </code>
      </a>
      , or
      <a class="link" href="enum.html" title="13.3.5 The ENUM Type">
       <code class="literal">
        ENUM
       </code>
      </a>
      ).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_fields-terminated-by">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-terminated-by">
       <code class="option">
        --fields-terminated-by
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        char
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099243920">
     </a>
     <a class="indexterm" name="idm46045099242464">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for fields-terminated-by">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --fields-terminated-by=char
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           \t (tab)
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      The string passed to this option is used to separate column
            values. The default value is a tab character
            (
      <code class="literal">
       \t
      </code>
      ).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_help">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_help">
       <code class="option">
        --help
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099227456">
     </a>
     <a class="indexterm" name="idm46045099225968">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for help">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --help
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Display help text and exit.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_hex">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_hex">
       <code class="option">
        --hex
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099216272">
     </a>
     <a class="indexterm" name="idm46045099214784">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for hex">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --hex
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      If this option is used, all binary values are output in
            hexadecimal format.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ignore-extended-pk-updates">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ignore-extended-pk-updates">
       <code class="option">
        --ignore-extended-pk-updates
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099204944">
     </a>
     <a class="indexterm" name="idm46045099203440">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ignore-extended-pk-updates">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ignore-extended-pk-updates[=0|1]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_allow-pk-changes">
       <code class="option">
        --allow-pk-changes
       </code>
      </a>
      ,
            columns which become part of a table's primary key must
            not be updated while the backup is being taken; such columns
            should keep the same values from the time values are
            inserted into them until the rows containing the values are
            deleted. If
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      encounters
            updates to these columns when restoring a backup, the
            restore fails. Because some applications may set values for
            all columns when updating a row, even when some column
            values are not changed, the backup may include log events
            appearing to update columns which are not in fact modified.
            In such cases you can set
      <code class="option">
       --ignore-extended-pk-updates
      </code>
      to
      <code class="literal">
       1
      </code>
      , forcing
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to ignore such updates.
     </p>
     <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Important
      </div>
      <p>
       When causing these updates to be ignored, the user is
              responsible for ensuring that there are no updates to the
              values of any columns that become part of the primary key.
      </p>
     </div>
     <p>
      For more information, see the description of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_allow-pk-changes">
       <code class="option">
        --allow-pk-changes
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_include-databases">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-databases">
       <code class="option">
        --include-databases
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        db-list
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099176272">
     </a>
     <a class="indexterm" name="idm46045099174816">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for include-databases">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --include-databases=list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Comma-delimited list of one or more databases to restore.
            Often used together with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-tables">
       <code class="option">
        --include-tables
       </code>
      </a>
      ; see
            the description of that option for further information and
            examples.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_include-stored-grants">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-stored-grants">
       <code class="option">
        --include-stored-grants
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099159280">
     </a>
     <a class="indexterm" name="idm46045099157776">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for include-stored-grants">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --include-stored-grants
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      does not by default restore
            shared users and grants (see
      <a class="xref" href="mysql-cluster-privilege-synchronization.html" title="25.6.13 Privilege Synchronization and NDB_STORED_USER">
       Section 25.6.13, “Privilege Synchronization and NDB_STORED_USER”
      </a>
      )
            to the
      <code class="literal">
       ndb_sql_metadata
      </code>
      table. Specifying
            this option causes it to do so.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_include-tables">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-tables">
       <code class="option">
        --include-tables
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        table-list
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099145024">
     </a>
     <a class="indexterm" name="idm46045099143536">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for include-tables">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --include-tables=list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Comma-delimited list of tables to restore; each table
            reference must include the database name.
     </p>
     <p>
      When
      <code class="option">
       --include-databases
      </code>
      or
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_include-tables">
       <code class="option">
        --include-tables
       </code>
      </a>
      is
            used, only those databases or tables named by the option are
            restored; all other databases and tables are excluded by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      , and are not restored.
     </p>
     <p>
      The following table shows several invocations of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      using
      <code class="option">
       --include-*
      </code>
      options (other options possibly
            required have been omitted for clarity), and the effects
            these have on restoring from an NDB Cluster backup:
     </p>
     <div class="table">
      <a name="idm46045099126032">
      </a>
      <p class="title">
       <b>
        Table 25.24 Several invocations of ndb_restore using --include-*
              options, and their effects on restoring from an NDB Cluster
backup.
       </b>
      </p>
      <div class="table-contents">
       <table>
        <colgroup>
         <col style="width: 50%"/>
         <col style="width: 50%"/>
        </colgroup>
        <thead>
         <tr>
          <th>
           Option
          </th>
          <th>
           Result
          </th>
         </tr>
        </thead>
        <tbody>
         <tr>
          <td>
           <code class="option">
            --include-databases=db1
           </code>
          </td>
          <td>
           Only tables in database
           <code class="literal">
            db1
           </code>
           are restored; all tables
                  in all other databases are ignored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --include-databases=db1,db2
           </code>
           (or
           <code class="option">
            --include-databases=db1
           </code>
           <code class="option">
            --include-databases=db2
           </code>
           )
          </td>
          <td>
           Only tables in databases
           <code class="literal">
            db1
           </code>
           and
           <code class="literal">
            db2
           </code>
           are restored; all tables in all
                  other databases are ignored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --include-tables=db1.t1
           </code>
          </td>
          <td>
           Only table
           <code class="literal">
            t1
           </code>
           in database
           <code class="literal">
            db1
           </code>
           is
                  restored; no other tables in
           <code class="literal">
            db1
           </code>
           or
                  in any other database are restored
          </td>
         </tr>
         <tr>
          <td>
           <code class="option">
            --include-tables=db1.t2,db2.t1
           </code>
           (or
           <code class="option">
            --include-tables=db1.t2
           </code>
           <code class="option">
            --include-tables=db2.t1
           </code>
           )
          </td>
          <td>
           Only the table
           <code class="literal">
            t2
           </code>
           in database
           <code class="literal">
            db1
           </code>
           and the table
           <code class="literal">
            t1
           </code>
           in database
           <code class="literal">
            db2
           </code>
           are restored; no other tables
                  in
           <code class="literal">
            db1
           </code>
           ,
           <code class="literal">
            db2
           </code>
           , or
                  any other database are restored
          </td>
         </tr>
        </tbody>
       </table>
      </div>
     </div>
     <br class="table-break"/>
     <p>
      You can also use these two options together. For example,
            the following causes all tables in databases
      <code class="literal">
       db1
      </code>
      and
      <code class="literal">
       db2
      </code>
      , together
            with the tables
      <code class="literal">
       t1
      </code>
      and
      <code class="literal">
       t2
      </code>
      in database
      <code class="literal">
       db3
      </code>
      , to
            be restored (and no other databases or tables):
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa45029379"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token punctuation">[</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">]</span> <span class="token constant">--include-databases</span><span class="token attr-value"><span class="token punctuation">=</span>db1,db2</span> <span class="token constant">--include-tables</span><span class="token attr-value"><span class="token punctuation">=</span>db3.t1,db3.t2</span></code></pre>
     </div>
     <p>
      (Again we have omitted other, possibly required, options in
            the example just shown.)
     </p>
     <p>
      It also possible to restore only selected databases, or
            selected tables from a single database, without any
      <code class="option">
       --include-*
      </code>
      (or
      <code class="option">
       --exclude-*
      </code>
      ) options, using the syntax
            shown here:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa4741059"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">ndb_restore <em class="replaceable">other_options</em> <em class="replaceable">db_name</em><span class="token punctuation">,</span><span class="token punctuation">[</span><em class="replaceable">db_name</em><span class="token punctuation">[</span><span class="token punctuation">,</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">]</span> | <em class="replaceable">tbl_name</em><span class="token punctuation">[</span><span class="token punctuation">,</span><em class="replaceable">tbl_name</em><span class="token punctuation">]</span><span class="token punctuation">[</span><span class="token punctuation">,</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">]</span><span class="token punctuation">]</span></code></pre>
     </div>
     <p>
      In other words, you can specify either of the following to
            be restored:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         All tables from one or more databases
        </p>
       </li>
       <li class="listitem">
        <p>
         One or more tables from a single database
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_lines-terminated-by">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_lines-terminated-by">
       <code class="option">
        --lines-terminated-by
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        char
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045099084672">
     </a>
     <a class="indexterm" name="idm46045099083216">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for lines-terminated-by">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --lines-terminated-by=char
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           \n (linebreak)
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Specifies the string used to end each line of output. The
            default is a linefeed character (
      <code class="literal">
       \n
      </code>
      ).
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_login-path">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_login-path">
       <code class="option">
        --login-path
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099068192">
     </a>
     <a class="indexterm" name="idm46045099066704">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for login-path">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --login-path=path
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Read given path from login file.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_no-login-paths">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_no-login-paths">
       <code class="option">
        --no-login-paths
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099052368">
     </a>
     <a class="indexterm" name="idm46045099050880">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-login-paths">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-login-paths
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Skips reading options from the login path file.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_lossy-conversions">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_lossy-conversions">
       <code class="option">
        --lossy-conversions
       </code>
      </a>
      ,
      <code class="option">
       -L
      </code>
     </p>
     <a class="indexterm" name="idm46045099040752">
     </a>
     <a class="indexterm" name="idm46045099039296">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for lossy-conversions">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --lossy-conversions
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option is intended to complement the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_promote-attributes">
       <code class="option">
        --promote-attributes
       </code>
      </a>
      option. Using
      <code class="option">
       --lossy-conversions
      </code>
      allows
            lossy conversions of column values (type demotions or
            changes in sign) when restoring data from backup. With some
            exceptions, the rules governing demotion are the same as for
            MySQL replication; see
      <a class="xref" href="replication-features-differing-tables.html#replication-features-different-data-types" title="19.5.1.9.2 Replication of Columns Having Different Data Types">
       Section 19.5.1.9.2, “Replication of Columns Having Different Data Types”
      </a>
      ,
            for information about specific type conversions currently
            supported by attribute demotion.
     </p>
     <p>
      This option also makes it possible to restore a
      <code class="literal">
       NULL
      </code>
      column as
      <code class="literal">
       NOT
            NULL
      </code>
      . The column must not contain any
      <code class="literal">
       NULL
      </code>
      entries; otherwise
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      stops with an error.
     </p>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      reports any truncation of
            data that it performs during lossy conversions once per
            attribute and column.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_no-binlog">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_no-binlog">
       <code class="option">
        --no-binlog
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045099020912">
     </a>
     <a class="indexterm" name="idm46045099019424">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-binlog">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-binlog
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option prevents any connected SQL nodes from writing
            data restored by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to their
            binary logs.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_no-restore-disk-objects">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_no-restore-disk-objects">
       <code class="option">
        --no-restore-disk-objects
       </code>
      </a>
      ,
      <code class="option">
       -d
      </code>
     </p>
     <a class="indexterm" name="idm46045099007872">
     </a>
     <a class="indexterm" name="idm46045099006368">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-restore-disk-objects">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-restore-disk-objects
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option stops
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      from
            restoring any NDB Cluster Disk Data objects, such as
            tablespaces and log file groups; see
      <a class="xref" href="mysql-cluster-disk-data.html" title="25.6.11 NDB Cluster Disk Data Tables">
       Section 25.6.11, “NDB Cluster Disk Data Tables”
      </a>
      , for more
            information about these.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_no-upgrade">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_no-upgrade">
       <code class="option">
        --no-upgrade
       </code>
      </a>
      ,
      <code class="option">
       -u
      </code>
     </p>
     <a class="indexterm" name="idm46045098994096">
     </a>
     <a class="indexterm" name="idm46045098992608">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-upgrade">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-upgrade
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to restore a
            backup,
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        VARCHAR
       </code>
      </a>
      columns
            created using the old fixed format are resized and recreated
            using the variable-width format now employed. This behavior
            can be overridden by specifying
      <code class="option">
       --no-upgrade
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-connectstring">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-connectstring">
       <code class="option">
        --ndb-connectstring
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098979888">
     </a>
     <a class="indexterm" name="idm46045098978432">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-connectstring">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-connectstring=connection_string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Set connection string for connecting to
      <a class="link" href="mysql-cluster-programs-ndb-mgmd.html" title="25.5.4 ndb_mgmd — The NDB Cluster Management Server Daemon">
       <span class="command">
        <strong>
         ndb_mgmd
        </strong>
       </span>
      </a>
      . Syntax:
      <code class="literal">
       [nodeid=
       <em class="replaceable">
        <code>
         id
        </code>
       </em>
       ;][host=]
       <em class="replaceable">
        <code>
         hostname
        </code>
       </em>
       [:
       <em class="replaceable">
        <code>
         port
        </code>
       </em>
       ]
      </code>
      .
            Overrides entries in
      <code class="literal">
       NDB_CONNECTSTRING
      </code>
      and
      <code class="filename">
       my.cnf
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-mgm-tls">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-mgm-tls">
       <code class="option">
        --ndb-mgm-tls
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098959392">
     </a>
     <a class="indexterm" name="idm46045098957904">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-mgm-tls">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-mgm-tls=level
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Enumeration
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           relaxed
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Valid Values
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            relaxed
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            strict
           </code>
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Sets the level of TLS support required to connect to the
            management server; one of
      <code class="literal">
       relaxed
      </code>
      or
      <code class="literal">
       strict
      </code>
      .
      <code class="literal">
       relaxed
      </code>
      (the
            default) means that a TLS connection is attempted, but
            success is not required;
      <code class="literal">
       strict
      </code>
      means
            that TLS is required to connect.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-mgmd-host">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-mgmd-host">
       <code class="option">
        --ndb-mgmd-host
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098936848">
     </a>
     <a class="indexterm" name="idm46045098935360">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-mgmd-host">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-mgmd-host=connection_string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Same as
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-connectstring">
       <code class="option">
        --ndb-connectstring
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-nodegroup-map">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-nodegroup-map">
       <code class="option">
        --ndb-nodegroup-map
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        map
       </code>
      </em>
      ,
      <code class="option">
       -z
      </code>
     </p>
     <a class="indexterm" name="idm46045098919376">
     </a>
     <a class="indexterm" name="idm46045098917872">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-nodegroup-map">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-nodegroup-map=map
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Any value set for this option is ignored, and the option
            itself does nothing.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-nodeid">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-nodeid">
       <code class="option">
        --ndb-nodeid
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098908048">
     </a>
     <a class="indexterm" name="idm46045098906560">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-nodeid">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-nodeid=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Set node ID for this node, overriding any ID set by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-connectstring">
       <code class="option">
        --ndb-connectstring
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-optimized-node-selection">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-optimized-node-selection">
       <code class="option">
        --ndb-optimized-node-selection
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098891184">
     </a>
     <a class="indexterm" name="idm46045098889680">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-optimized-node-selection">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-optimized-node-selection
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Enable optimizations for selection of nodes for
            transactions. Enabled by default; use
      <code class="option">
       --skip-ndb-optimized-node-selection
      </code>
      to
            disable.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_ndb-tls-search-path">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_ndb-tls-search-path">
       <code class="option">
        --ndb-tls-search-path
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098879264">
     </a>
     <a class="indexterm" name="idm46045098877808">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ndb-tls-search-path">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ndb-tls-search-path=list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Path name
         </td>
        </tr>
        <tr>
         <th>
          Default Value (Unix)
         </th>
         <td>
          <code class="literal">
           $HOME/ndb-tls
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Default Value (Windows)
         </th>
         <td>
          <code class="literal">
           $HOMEDIR/ndb-tls
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Specify a list of directories to search for a CA file. On
            Unix platforms, the directory names are separated by colons
            (
      <code class="literal">
       :
      </code>
      ); on Windows systems, the semicolon
            character (
      <code class="literal">
       ;
      </code>
      ) is used as the separator. A
            directory reference may be relative or absolute; it may
            contain one or more environment variables, each denoted by a
            prefixed dollar sign (
      <code class="literal">
       $
      </code>
      ), and expanded
            prior to use.
     </p>
     <p>
      Searching begins with the leftmost named directory and
            proceeds from left to right until a file is found. An empty
            string denotes an empty search path, which causes all
            searches to fail. A string consisting of a single dot
            (
      <code class="literal">
       .
      </code>
      ) indicates that the search path
            limited to the current working directory.
     </p>
     <p>
      If no search path is supplied, the compiled-in default value
            is used. This value depends on the platform used: On
            Windows, this is
      <code class="literal">
       \ndb-tls
      </code>
      ; on other
            platforms (including Linux), it is
      <code class="literal">
       $HOME/ndb-tls
      </code>
      . This can be overridden by
            compiling NDB Cluster using
      <a class="link" href="source-configuration-options.html#option_cmake_with_ndb_tls_search_path">
       <code class="option">
        -DWITH_NDB_TLS_SEARCH_PATH
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_no-defaults">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_no-defaults">
       <code class="option">
        --no-defaults
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098854048">
     </a>
     <a class="indexterm" name="idm46045098852560">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-defaults">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-defaults
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Do not read default options from any option file other than
            login file.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_nodeid">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid">
       <code class="option">
        --nodeid
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
      ,
      <code class="option">
       -n
      </code>
     </p>
     <a class="indexterm" name="idm46045098841936">
     </a>
     <a class="indexterm" name="idm46045098840448">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for nodeid">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --nodeid=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           none
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Specify the node ID of the data node on which the backup was
            taken; required.
     </p>
     <p>
      When restoring to a cluster with different number of data
            nodes from that where the backup was taken, this information
            helps identify the correct set or sets of files to be
            restored to a given node. (In such cases, multiple files
            usually need to be restored to a single data node.) See
      <a class="ulink" href="/doc/refman/8.0/en/ndb-restore-different-number-nodes.html" target="_top">
       Restoring to a different number of data nodes
      </a>
      , for
            additional information and examples.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_num-slices">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_num-slices">
       <code class="option">
        --num-slices
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098823776">
     </a>
     <a class="indexterm" name="idm46045098822288">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for num-slices">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --num-slices=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           1024
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When restoring a backup by slices, this option sets the
            number of slices into which to divide the backup. This
            allows multiple instances of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to restore disjoint subsets in parallel, potentially
            reducing the amount of time required to perform the restore
            operation.
     </p>
     <p>
      A
      <span class="emphasis">
       <em>
        slice
       </em>
      </span>
      is a subset of the data in a
            given backup; that is, it is a set of fragments having the
            same slice ID, specified using the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_slice-id">
       <code class="option">
        --slice-id
       </code>
      </a>
      option. The
            two options must always be used together, and the value set
            by
      <code class="option">
       --slice-id
      </code>
      must always be less than the
            number of slices.
     </p>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      encounters fragments and
            assigns each one a fragment counter. When restoring by
            slices, a slice ID is assigned to each fragment; this slice
            ID is in the range 0 to 1 less than the number of slices.
            For a table that is not a
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        BLOB
       </code>
      </a>
      table, the slice to
            which a given fragment belongs is determined using the
            formula shown here:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-simple"><div class="docs-select-all right" id="sa27538780"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-simple"><span class="token punctuation">[</span><em class="replaceable">slice_ID</em><span class="token punctuation">]</span> <span class="token operator">=</span> <span class="token punctuation">[</span><em class="replaceable">fragment_counter</em><span class="token punctuation">]</span> <span class="token operator">%</span> <span class="token punctuation">[</span><em class="replaceable">number_of_slices</em><span class="token punctuation">]</span></code></pre>
     </div>
     <p>
      For a
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        BLOB
       </code>
      </a>
      table, a fragment
            counter is not used; the fragment number is used instead,
            along with the ID of the main table for the
      <code class="literal">
       BLOB
      </code>
      table (recall that
      <code class="literal">
       NDB
      </code>
      stores
      <em class="replaceable">
       <code>
        BLOB
       </code>
      </em>
      values in a separate table
            internally). In this case, the slice ID for a given fragment
            is calculated as shown here:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-simple"><div class="docs-select-all right" id="sa28230096"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-simple"><span class="token punctuation">[</span><em class="replaceable">slice_ID</em><span class="token punctuation">]</span> <span class="token operator">=</span>
<span class="token punctuation">(</span><span class="token punctuation">[</span><em class="replaceable">main_table_ID</em><span class="token punctuation">]</span> <span class="token operator">+</span> <span class="token punctuation">[</span><em class="replaceable">fragment_ID</em><span class="token punctuation">]</span><span class="token punctuation">)</span> <span class="token operator">%</span> <span class="token punctuation">[</span><em class="replaceable">number_of_slices</em><span class="token punctuation">]</span></code></pre>
     </div>
     <p>
      Thus, restoring by
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      slices means
            running
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      instances of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      , all with
      <code class="option">
       --num-slices=
       <em class="replaceable">
        <code>
         N
        </code>
       </em>
      </code>
      (along with any other necessary options) and one each with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_slice-id">
       <code class="option">
        --slice-id=1
       </code>
      </a>
      ,
      <code class="option">
       --slice-id=2
      </code>
      ,
      <code class="option">
       --slice-id=3
      </code>
      , and so on through
      <code class="option">
       slice-id=
       <em class="replaceable">
        <code>
         N
        </code>
       </em>
       -1
      </code>
      .
     </p>
     <p>
      <b>
       Example.
      </b>
      Assume that you want to restore a backup named
      <code class="filename">
       BACKUP-1
      </code>
      , found in the default
              directory
      <code class="filename">
       /var/lib/mysql-cluster/BACKUP/BACKUP-3
      </code>
      on the node file system on each data node, to a cluster
              with four data nodes having the node IDs 1, 2, 3, and 4.
              To perform this operation using five slices, execute the
              sets of commands shown in the following list:
     </p>
     <div class="orderedlist">
      <ol class="orderedlist" type="1">
       <li class="listitem">
        <p>
         Restore the cluster metadata using
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         as shown here:
        </p>
        <div class="copytoclipboard-wrapper">
         <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa78573201"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-m</span> <span class="token property">--disable-indexes</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/home/ndbuser/backups</span></code></pre>
        </div>
       </li>
       <li class="listitem">
        <p>
         Restore the cluster data to the data nodes invoking
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         as shown here:
        </p>
        <div class="copytoclipboard-wrapper">
         <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa68788424"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>0</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>1</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>2</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>3</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>4</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>

<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 2 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>0</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 2 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>1</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 2 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>2</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 2 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>3</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 2 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>4</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>

<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 3 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>0</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 3 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>1</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 3 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>2</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 3 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>3</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 3 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>4</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>

<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 4 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>0</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 4 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>1</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 4 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>2</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 4 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>3</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span>
<span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 4 <span class="token property">-r</span> <span class="token constant">--num-slices</span><span class="token attr-value"><span class="token punctuation">=</span>5</span> <span class="token constant">--slice-id</span><span class="token attr-value"><span class="token punctuation">=</span>4</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span></code></pre>
        </div>
        <p>
         All of the commands just shown in this step can be
                executed in parallel, provided there are enough slots
                for connections to the cluster (see the description for
                the
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-path">
          <code class="option">
           --backup-path
          </code>
         </a>
         option).
        </p>
       </li>
       <li class="listitem">
        <p>
         Restore indexes as usual, as shown here:
        </p>
        <div class="copytoclipboard-wrapper">
         <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa17741601"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">--rebuild-indexes</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span></code></pre>
        </div>
       </li>
       <li class="listitem">
        <p>
         Finally, restore the epoch, using the command shown
                here:
        </p>
        <div class="copytoclipboard-wrapper">
         <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa75584834"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">-b</span> 1 <span class="token property">-n</span> 1 <span class="token property">--restore-epoch</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span>/var/lib/mysql-cluster/BACKUP/BACKUP-1</span></code></pre>
        </div>
       </li>
      </ol>
     </div>
     <p>
      You should use slicing to restore the cluster data only; it
            is not necessary to employ
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_num-slices">
       <code class="option">
        --num-slices
       </code>
      </a>
      or
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_slice-id">
       <code class="option">
        --slice-id
       </code>
      </a>
      when
            restoring the metadata, indexes, or epoch information. If
            either or both of these options are used with the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      options controlling
            restoration of these, the program ignores them.
     </p>
     <p>
      The effects of using the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_parallelism">
       <code class="option">
        --parallelism
       </code>
      </a>
      option on
            the speed of restoration are independent of those produced
            by slicing or parallel restoration using multiple instances
            of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      (
      <code class="option">
       --parallelism
      </code>
      specifies the number of
            parallel transactions executed by a
      <span class="emphasis">
       <em>
        single
       </em>
      </span>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      thread), but it can be used together with either or both of
            these. You should be aware that increasing
      <code class="option">
       --parallelism
      </code>
      causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to impose a greater load on
            the cluster; if the system can handle this, restoration
            should complete even more quickly.
     </p>
     <p>
      The value of
      <code class="option">
       --num-slices
      </code>
      is not directly
            dependent on values relating to hardware such as number of
            CPUs or CPU cores, amount of RAM, and so forth, nor does it
            depend on the number of LDMs.
     </p>
     <p>
      It is possible to employ different values for this option on
            different data nodes as part of the same restoration; doing
            so should not in and of itself produce any ill effects.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_parallelism">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_parallelism">
       <code class="option">
        --parallelism
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
      ,
      <code class="option">
       -p
      </code>
     </p>
     <a class="indexterm" name="idm46045098733168">
     </a>
     <a class="indexterm" name="idm46045098731680">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for parallelism">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --parallelism=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           128
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           1024
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      uses single-row transactions
            to apply many rows concurrently. This parameter determines
            the number of parallel transactions (concurrent rows) that
            an instance of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      tries to use.
            By default, this is 128; the minimum is 1, and the maximum
            is 1024.
     </p>
     <p>
      The work of performing the inserts is parallelized across
            the threads in the data nodes involved. This mechanism is
            employed for restoring bulk data from the
      <code class="filename">
       .Data
      </code>
      file—that is, the fuzzy
            snapshot of the data; it is not used for building or
            rebuilding indexes. The change log is applied serially;
            index drops and builds are DDL operations and handled
            separately. There is no thread-level parallelism on the
            client side of the restore.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_preserve-trailing-spaces">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_preserve-trailing-spaces">
       <code class="option">
        --preserve-trailing-spaces
       </code>
      </a>
      ,
      <code class="option">
       -P
      </code>
     </p>
     <a class="indexterm" name="idm46045098707424">
     </a>
     <a class="indexterm" name="idm46045098705920">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for preserve-trailing-spaces">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --preserve-trailing-spaces
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Cause trailing spaces to be preserved when promoting a
            fixed-width character data type to its variable-width
            equivalent—that is, when promoting a
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        CHAR
       </code>
      </a>
      column value to
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        VARCHAR
       </code>
      </a>
      , or a
      <code class="literal">
       BINARY
      </code>
      column value to
      <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
       <code class="literal">
        VARBINARY
       </code>
      </a>
      . Otherwise, any
            trailing spaces are dropped from such column values when
            they are inserted into the new columns.
     </p>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       Although you can promote
       <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
        <code class="literal">
         CHAR
        </code>
       </a>
       columns to
       <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
        <code class="literal">
         VARCHAR
        </code>
       </a>
       and
       <code class="literal">
        BINARY
       </code>
       columns to
       <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
        <code class="literal">
         VARBINARY
        </code>
       </a>
       , you cannot
              promote
       <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
        <code class="literal">
         VARCHAR
        </code>
       </a>
       columns to
       <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
        <code class="literal">
         CHAR
        </code>
       </a>
       or
       <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
        <code class="literal">
         VARBINARY
        </code>
       </a>
       columns to
       <code class="literal">
        BINARY
       </code>
       .
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print">
       <code class="option">
        --print
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098681456">
     </a>
     <a class="indexterm" name="idm46045098679968">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to print all data,
            metadata, and logs to
      <code class="literal">
       stdout
      </code>
      . Equivalent
            to using the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-data">
       <code class="option">
        --print-data
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-meta">
       <code class="option">
        --print-meta
       </code>
      </a>
      , and
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-log">
       <code class="option">
        --print-log
       </code>
      </a>
      options
            together.
     </p>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       Use of
       <code class="option">
        --print
       </code>
       or any of the
       <code class="option">
        --print_*
       </code>
       options is in effect performing
              a dry run. Including one or more of these options causes
              any output to be redirected to
       <code class="literal">
        stdout
       </code>
       ;
              in such cases,
       <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
        <span class="command">
         <strong>
          ndb_restore
         </strong>
        </span>
       </a>
       makes no
              attempt to restore data or metadata to an NDB Cluster.
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print-data">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-data">
       <code class="option">
        --print-data
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098661104">
     </a>
     <a class="indexterm" name="idm46045098659616">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-data">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-data
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Cause
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to direct its output to
      <code class="literal">
       stdout
      </code>
      . Often used together with one or
            more of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_tab">
       <code class="option">
        --tab
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-enclosed-by">
       <code class="option">
        --fields-enclosed-by
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-optionally-enclosed-by">
       <code class="option">
        --fields-optionally-enclosed-by
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_fields-terminated-by">
       <code class="option">
        --fields-terminated-by
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_hex">
       <code class="option">
        --hex
       </code>
      </a>
      , and
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_append">
       <code class="option">
        --append
       </code>
      </a>
      .
     </p>
     <p>
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        TEXT
       </code>
      </a>
      and
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        BLOB
       </code>
      </a>
      column values are always
            truncated. Such values are truncated to the first 256 bytes
            in the output. This cannot currently be overridden when
            using
      <code class="option">
       --print-data
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print-defaults">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-defaults">
       <code class="option">
        --print-defaults
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098638512">
     </a>
     <a class="indexterm" name="idm46045098637024">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-defaults">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-defaults
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Print program argument list and exit.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print-log">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-log">
       <code class="option">
        --print-log
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098627424">
     </a>
     <a class="indexterm" name="idm46045098625936">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-log">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-log
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Cause
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to output its log to
      <code class="literal">
       stdout
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print-meta">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-meta">
       <code class="option">
        --print-meta
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098614320">
     </a>
     <a class="indexterm" name="idm46045098612832">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-meta">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-meta
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Print all metadata to
      <code class="literal">
       stdout
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_print-sql-log">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-sql-log">
       <code class="option">
        print-sql-log
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098602368">
     </a>
     <a class="indexterm" name="idm46045098600880">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-sql-log">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-sql-log
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Log SQL statements to
      <code class="literal">
       stdout
      </code>
      . Use the
            option to enable; normally this behavior is disabled. The
            option checks before attempting to log whether all the
            tables being restored have explicitly defined primary keys;
            queries on a table having only the hidden primary key
            implemented by
      <code class="literal">
       NDB
      </code>
      cannot be converted to
            valid SQL.
     </p>
     <p>
      This option does not work with tables having
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        BLOB
       </code>
      </a>
      columns.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_progress-frequency">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_progress-frequency">
       <code class="option">
        --progress-frequency
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098587232">
     </a>
     <a class="indexterm" name="idm46045098585776">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for progress-frequency">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --progress-frequency=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           65535
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Print a status report each
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      seconds while the backup is in progress. 0 (the default)
            causes no status reports to be printed. The maximum is
            65535.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_promote-attributes">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_promote-attributes">
       <code class="option">
        --promote-attributes
       </code>
      </a>
      ,
      <code class="option">
       -A
      </code>
     </p>
     <a class="indexterm" name="idm46045098565760">
     </a>
     <a class="indexterm" name="idm46045098564304">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for promote-attributes">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --promote-attributes
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      supports limited
      <span class="firstterm">
       attribute promotion
      </span>
      in
            much the same way that it is supported by MySQL replication;
            that is, data backed up from a column of a given type can
            generally be restored to a column using a
      <span class="quote">
       “
       <span class="quote">
        larger,
            similar
       </span>
       ”
      </span>
      type. For example, data from a
      <code class="literal">
       CHAR(20)
      </code>
      column can be restored to a
            column declared as
      <code class="literal">
       VARCHAR(20)
      </code>
      ,
      <code class="literal">
       VARCHAR(30)
      </code>
      , or
      <code class="literal">
       CHAR(30)
      </code>
      ; data from a
      <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
       <code class="literal">
        MEDIUMINT
       </code>
      </a>
      column can be
            restored to a column of type
      <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
       <code class="literal">
        INT
       </code>
      </a>
      or
      <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
       <code class="literal">
        BIGINT
       </code>
      </a>
      . See
      <a class="xref" href="replication-features-differing-tables.html#replication-features-different-data-types" title="19.5.1.9.2 Replication of Columns Having Different Data Types">
       Section 19.5.1.9.2, “Replication of Columns Having Different Data Types”
      </a>
      ,
            for a table of type conversions currently supported by
            attribute promotion.
     </p>
     <p>
      This option also makes it possible to restore a
      <code class="literal">
       NOT
            NULL
      </code>
      column as
      <code class="literal">
       NULL
      </code>
      .
     </p>
     <p>
      Attribute promotion by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      must
            be enabled explicitly, as follows:
     </p>
     <div class="orderedlist">
      <ol class="orderedlist" type="1">
       <li class="listitem">
        <p>
         Prepare the table to which the backup is to be restored.
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         cannot be used to
                re-create the table with a different definition from the
                original; this means that you must either create the
                table manually, or alter the columns which you wish to
                promote using
         <a class="link" href="alter-table.html" title="15.1.9 ALTER TABLE Statement">
          <code class="literal">
           ALTER TABLE
          </code>
         </a>
         after restoring the table metadata but before restoring
                the data.
        </p>
       </li>
       <li class="listitem">
        <p>
         Invoke
         <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
          <span class="command">
           <strong>
            ndb_restore
           </strong>
          </span>
         </a>
         with the
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_promote-attributes">
          <code class="option">
           --promote-attributes
          </code>
         </a>
         option (short form
         <code class="option">
          -A
         </code>
         ) when restoring
                the table data. Attribute promotion does not occur if
                this option is not used; instead, the restore operation
                fails with an error.
        </p>
       </li>
      </ol>
     </div>
     <p>
      When converting between character data types and
      <code class="literal">
       TEXT
      </code>
      or
      <code class="literal">
       BLOB
      </code>
      , only
            conversions between character types
            (
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        CHAR
       </code>
      </a>
      and
      <a class="link" href="char.html" title="13.3.2 The CHAR and VARCHAR Types">
       <code class="literal">
        VARCHAR
       </code>
      </a>
      ) and binary types
            (
      <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
       <code class="literal">
        BINARY
       </code>
      </a>
      and
      <a class="link" href="binary-varbinary.html" title="13.3.3 The BINARY and VARBINARY Types">
       <code class="literal">
        VARBINARY
       </code>
      </a>
      ) can be performed
            at the same time. For example, you cannot promote an
      <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
       <code class="literal">
        INT
       </code>
      </a>
      column to
      <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
       <code class="literal">
        BIGINT
       </code>
      </a>
      while promoting a
      <code class="literal">
       VARCHAR
      </code>
      column to
      <code class="literal">
       TEXT
      </code>
      in the same invocation of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      .
     </p>
     <p>
      Converting between
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        TEXT
       </code>
      </a>
      columns using different character sets is not supported, and
            is expressly disallowed.
     </p>
     <p>
      When performing conversions of character or binary types to
      <code class="literal">
       TEXT
      </code>
      or
      <code class="literal">
       BLOB
      </code>
      with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      , you may notice that it
            creates and uses one or more staging tables named
      <code class="literal">
       <em class="replaceable">
        <code>
         table_name
        </code>
       </em>
       $ST
       <em class="replaceable">
        <code>
         node_id
        </code>
       </em>
      </code>
      .
            These tables are not needed afterwards, and are normally
            deleted by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      following a
            successful restoration.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_rebuild-indexes">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rebuild-indexes">
       <code class="option">
        --rebuild-indexes
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098512640">
     </a>
     <a class="indexterm" name="idm46045098511152">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for rebuild-indexes">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --rebuild-indexes
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Enable multithreaded rebuilding of the ordered indexes while
            restoring a native
      <code class="literal">
       NDB
      </code>
      backup. The number
            of threads used for building ordered indexes by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      with this option is
            controlled by the
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-buildindexthreads">
       <code class="literal">
        BuildIndexThreads
       </code>
      </a>
      data node configuration parameter and the number of LDMs.
     </p>
     <a class="indexterm" name="idm46045098500224">
     </a>
     <p>
      It is necessary to use this option only for the first run of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      ; this causes all ordered
            indexes to be rebuilt without using
      <code class="option">
       --rebuild-indexes
      </code>
      again when restoring
            subsequent nodes. You should use this option prior to
            inserting new rows into the database; otherwise, it is
            possible for a row to be inserted that later causes a unique
            constraint violation when trying to rebuild the indexes.
     </p>
     <p>
      Building of ordered indices is parallelized with the number
            of LDMs by default. Offline index builds performed during
            node and system restarts can be made faster using the
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-buildindexthreads">
       <code class="literal">
        BuildIndexThreads
       </code>
      </a>
      data node configuration parameter; this parameter has no
            effect on dropping and rebuilding of indexes by
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      , which is performed online.
     </p>
     <p>
      Rebuilding of unique indexes uses disk write bandwidth for
            redo logging and local checkpointing. An insufficient amount
            of this bandwidth can lead to redo buffer overload or log
            overload errors. In such cases you can run
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <code class="option">
       --rebuild-indexes
      </code>
      again; the process
            resumes at the point where the error occurred. You can also
            do this when you have encountered temporary errors. You can
            repeat execution of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <code class="option">
       --rebuild-indexes
      </code>
      indefinitely; you may be
            able to stop such errors by reducing the value of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_parallelism">
       <code class="option">
        --parallelism
       </code>
      </a>
      . If the
            problem is insufficient space, you can increase the size of
            the redo log
            (
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-fragmentlogfilesize">
       <code class="literal">
        FragmentLogFileSize
       </code>
      </a>
      node configuration parameter), or you can increase the speed
            at which LCPs are performed
            (
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-maxdiskwritespeed">
       <code class="literal">
        MaxDiskWriteSpeed
       </code>
      </a>
      and related parameters), in order to free space more
            quickly.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_remap-column">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_remap-column">
       <code class="option">
        --remap-column=
        <em class="replaceable">
         <code>
          db
         </code>
        </em>
        .
        <em class="replaceable">
         <code>
          tbl
         </code>
        </em>
        .
        <em class="replaceable">
         <code>
          col
         </code>
        </em>
        :
        <em class="replaceable">
         <code>
          fn
         </code>
        </em>
        :
        <em class="replaceable">
         <code>
          args
         </code>
        </em>
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098480656">
     </a>
     <a class="indexterm" name="idm46045098479168">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for remap-column">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --remap-column=string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When used together with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-data">
       <code class="option">
        --restore-data
       </code>
      </a>
      , this
            option applies a function to the value of the indicated
            column. Values in the argument string are listed here:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <em class="replaceable">
          <code>
           db
          </code>
         </em>
         : Database name, following
                any renames performed by
         <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rewrite-database">
          <code class="option">
           --rewrite-database
          </code>
         </a>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <em class="replaceable">
          <code>
           tbl
          </code>
         </em>
         : Table name.
        </p>
       </li>
       <li class="listitem">
        <p>
         <em class="replaceable">
          <code>
           col
          </code>
         </em>
         : Name of the column to be
                updated. This column must be of type
         <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
          <code class="literal">
           INT
          </code>
         </a>
         or
         <a class="link" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
          <code class="literal">
           BIGINT
          </code>
         </a>
         . The column can
                also be but is not required to be
         <code class="literal">
          UNSIGNED
         </code>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <em class="replaceable">
          <code>
           fn
          </code>
         </em>
         : Function name; currently,
                the only supported name is
         <code class="literal">
          offset
         </code>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <em class="replaceable">
          <code>
           args
          </code>
         </em>
         : Arguments supplied to
                the function. Currently, only a single argument, the
                size of the offset to be added by the
         <code class="literal">
          offset
         </code>
         function, is supported.
                Negative values are supported. The size of the argument
                cannot exceed that of the signed variant of the
                column's type; for example, if
         <em class="replaceable">
          <code>
           col
          </code>
         </em>
         is an
         <code class="literal">
          INT
         </code>
         column, then the allowed range of
                the argument passed to the
         <code class="literal">
          offset
         </code>
         function is
         <code class="literal">
          -2147483648
         </code>
         to
         <code class="literal">
          2147483647
         </code>
         (see
         <a class="xref" href="integer-types.html" title="13.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT">
          Section 13.1.2, “Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT,
        MEDIUMINT, BIGINT”
         </a>
         ).
        </p>
        <p>
         If applying the offset value to the column would cause
                an overflow or underflow, the restore operation fails.
                This could happen, for example, if the column is a
         <code class="literal">
          BIGINT
         </code>
         , and the option attempts to
                apply an offset value of 8 on a row in which the column
                value is 4294967291, since
         <code class="literal">
          4294967291 + 8
                = 4294967299 &gt; 4294967295
         </code>
         .
        </p>
       </li>
      </ul>
     </div>
     <p>
      This option can be useful when you wish to merge data stored
            in multiple source instances of NDB Cluster (all using the
            same schema) into a single destination NDB Cluster, using
            NDB native backup (see
      <a class="xref" href="mysql-cluster-backup-using-management-client.html" title="25.6.8.2 Using The NDB Cluster Management Client to Create a Backup">
       Section 25.6.8.2, “Using The NDB Cluster Management Client to Create a Backup”
      </a>
      )
            and
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to merge the data, where
            primary and unique key values are overlapping between source
            clusters, and it is necessary as part of the process to
            remap these values to ranges that do not overlap. It may
            also be necessary to preserve other relationships between
            tables. To fulfill such requirements, it is possible to use
            the option multiple times in the same invocation of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to remap columns of different
            tables, as shown here:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa33435437"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">--restore-data</span> <span class="token constant">--remap-column</span><span class="token attr-value"><span class="token punctuation">=</span>hr.employee.id:offset:1000</span> \
    <span class="token constant">--remap-column</span><span class="token attr-value"><span class="token punctuation">=</span>hr.manager.id:offset:1000</span> <span class="token constant">--remap-column</span><span class="token attr-value"><span class="token punctuation">=</span>hr.firstaiders.id:offset:1000</span></code></pre>
     </div>
     <p>
      (Other options not shown here may also be used.)
     </p>
     <p>
      <code class="option">
       --remap-column
      </code>
      can also be used to update
            multiple columns of the same table. Combinations of multiple
            tables and columns are possible. Different offset values can
            also be used for different columns of the same table, like
            this:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa77532522"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token property">--restore-data</span> <span class="token constant">--remap-column</span><span class="token attr-value"><span class="token punctuation">=</span>hr.employee.salary:offset:10000</span> \
    <span class="token constant">--remap-column</span><span class="token attr-value"><span class="token punctuation">=</span>hr.employee.hours:offset:-10</span></code></pre>
     </div>
     <p>
      When source backups contain duplicate tables which should
            not be merged, you can handle this by using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-tables">
       <code class="option">
        --exclude-tables
       </code>
      </a>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_exclude-databases">
       <code class="option">
        --exclude-databases
       </code>
      </a>
      , or
            by some other means in your application.
     </p>
     <p>
      Information about the structure and other characteristics of
            tables to be merged can obtained using
      <a class="link" href="show-create-table.html" title="15.7.7.11 SHOW CREATE TABLE Statement">
       <code class="literal">
        SHOW CREATE TABLE
       </code>
      </a>
      ; the
      <a class="link" href="mysql-cluster-programs-ndb-desc.html" title="25.5.9 ndb_desc — Describe NDB Tables">
       <span class="command">
        <strong>
         ndb_desc
        </strong>
       </span>
      </a>
      tool; and
      <a class="link" href="aggregate-functions.html#function_max">
       <code class="literal">
        MAX()
       </code>
      </a>
      ,
      <a class="link" href="aggregate-functions.html#function_min">
       <code class="literal">
        MIN()
       </code>
      </a>
      ,
      <a class="link" href="information-functions.html#function_last-insert-id">
       <code class="literal">
        LAST_INSERT_ID()
       </code>
      </a>
      , and other
            MySQL functions.
     </p>
     <p>
      Replication of changes from merged to unmerged tables, or
            from unmerged to merged tables, in separate instances of NDB
            Cluster is not supported.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_restore-data">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-data">
       <code class="option">
        --restore-data
       </code>
      </a>
      ,
      <code class="option">
       -r
      </code>
     </p>
     <a class="indexterm" name="idm46045098424896">
     </a>
     <a class="indexterm" name="idm46045098423408">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for restore-data">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --restore-data
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Output
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      table data and logs.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_restore-epoch">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-epoch">
       <code class="option">
        --restore-epoch
       </code>
      </a>
      ,
      <code class="option">
       -e
      </code>
     </p>
     <a class="indexterm" name="idm46045098412096">
     </a>
     <a class="indexterm" name="idm46045098410608">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for restore-epoch">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --restore-epoch
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Add (or restore) epoch information to the cluster
            replication status table. This is useful for starting
            replication on an NDB Cluster replica. When this option is
            used, the row in the
      <code class="literal">
       mysql.ndb_apply_status
      </code>
      having
      <code class="literal">
       0
      </code>
      in the
      <code class="literal">
       id
      </code>
      column is
            updated if it already exists; such a row is inserted if it
            does not already exist. (See
      <a class="xref" href="mysql-cluster-replication-backups.html" title="25.7.9 NDB Cluster Backups With NDB Cluster Replication">
       Section 25.7.9, “NDB Cluster Backups With NDB Cluster Replication”
      </a>
      .)
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_restore-meta">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-meta">
       <code class="option">
        --restore-meta
       </code>
      </a>
      ,
      <code class="option">
       -m
      </code>
     </p>
     <a class="indexterm" name="idm46045098397328">
     </a>
     <a class="indexterm" name="idm46045098395840">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for restore-meta">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --restore-meta
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to print
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      table metadata.
     </p>
     <p>
      The first time you run the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      restoration program, you also need to restore the metadata.
            In other words, you must re-create the database
            tables—this can be done by running it with the
      <code class="option">
       --restore-meta
      </code>
      (
      <code class="option">
       -m
      </code>
      )
            option. Restoring the metadata need be done only on a single
            data node; this is sufficient to restore it to the entire
            cluster.
     </p>
     <p>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      uses the default number of
            partitions for the target cluster, unless the number of
            local data manager threads is also changed from what it was
            for data nodes in the original cluster.
     </p>
     <p>
      When using this option, it is recommended that auto
            synchronization be disabled by setting
      <a class="link" href="mysql-cluster-options-variables.html#sysvar_ndb_metadata_check">
       <code class="literal">
        ndb_metadata_check=OFF
       </code>
      </a>
      until
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      has completed restoring
            the metadata, after which it can it turned on again to
            synchronize objects newly created in the NDB dictionary.
     </p>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       The cluster should have an empty database when starting to
              restore a backup. (In other words, you should start the
              data nodes with
       <a class="link" href="mysql-cluster-programs-ndbd.html#option_ndbd_initial">
        <code class="option">
         --initial
        </code>
       </a>
       prior to performing the restore.)
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_restore-privilege-tables">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-privilege-tables">
       <code class="option">
        --restore-privilege-tables
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098373440">
     </a>
     <a class="indexterm" name="idm46045098371936">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for restore-privilege-tables">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --restore-privilege-tables
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Deprecated
         </th>
         <td>
          Yes
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      No longer used.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_rewrite-database">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_rewrite-database">
       <code class="option">
        --rewrite-database
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        olddb,newdb
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098359920">
     </a>
     <a class="indexterm" name="idm46045098358432">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for rewrite-database">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --rewrite-database=string
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           none
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option makes it possible to restore to a database
            having a different name from that used in the backup. For
            example, if a backup is made of a database named
      <code class="literal">
       products
      </code>
      , you can restore the data it
            contains to a database named
      <code class="literal">
       inventory
      </code>
      ,
            use this option as shown here (omitting any other options
            that might be required):
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa7017297"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_restore</span> <span class="token constant">--rewrite-database</span><span class="token attr-value"><span class="token punctuation">=</span>product,inventory</span></code></pre>
     </div>
     <p>
      The option can be employed multiple times in a single
            invocation of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      . Thus it is
            possible to restore simultaneously from a database named
      <code class="literal">
       db1
      </code>
      to a database named
      <code class="literal">
       db2
      </code>
      and from a database named
      <code class="literal">
       db3
      </code>
      to one named
      <code class="literal">
       db4
      </code>
      using
      <code class="option">
       --rewrite-database=db1,db2
            --rewrite-database=db3,db4
      </code>
      . Other
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      options may be used between
            multiple occurrences of
      <code class="option">
       --rewrite-database
      </code>
      .
     </p>
     <p>
      In the event of conflicts between multiple
      <code class="option">
       --rewrite-database
      </code>
      options, the last
      <code class="option">
       --rewrite-database
      </code>
      option used, reading
            from left to right, is the one that takes effect. For
            example, if
      <code class="option">
       --rewrite-database=db1,db2
            --rewrite-database=db1,db3
      </code>
      is used, only
      <code class="option">
       --rewrite-database=db1,db3
      </code>
      is honored, and
      <code class="option">
       --rewrite-database=db1,db2
      </code>
      is ignored. It
            is also possible to restore from multiple databases to a
            single database, so that
      <code class="option">
       --rewrite-database=db1,db3
            --rewrite-database=db2,db3
      </code>
      restores all tables and
            data from databases
      <code class="literal">
       db1
      </code>
      and
      <code class="literal">
       db2
      </code>
      into database
      <code class="literal">
       db3
      </code>
      .
     </p>
     <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Important
      </div>
      <p>
       When restoring from multiple backup databases into a
              single target database using
       <code class="option">
        --rewrite-database
       </code>
       , no check is made for
              collisions between table or other object names, and the
              order in which rows are restored is not guaranteed. This
              means that it is possible in such cases for rows to be
              overwritten and updates to be lost.
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_skip-broken-objects">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_skip-broken-objects">
       <code class="option">
        --skip-broken-objects
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098327152">
     </a>
     <a class="indexterm" name="idm46045098325696">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for skip-broken-objects">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --skip-broken-objects
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to ignore
            corrupt tables while reading a native
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      backup, and to continue
            restoring any remaining tables (that are not also
            corrupted). Currently, the
      <code class="option">
       --skip-broken-objects
      </code>
      option works only in
            the case of missing blob parts tables.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_skip-table-check">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_skip-table-check">
       <code class="option">
        --skip-table-check
       </code>
      </a>
      ,
      <code class="option">
       -s
      </code>
     </p>
     <a class="indexterm" name="idm46045098312368">
     </a>
     <a class="indexterm" name="idm46045098310880">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for skip-table-check">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --skip-table-check
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      It is possible to restore data without restoring table
            metadata. By default when doing this,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      fails with an error if a
            mismatch is found between the table data and the table
            schema; this option overrides that behavior.
     </p>
     <p>
      Some of the restrictions on mismatches in column definitions
            when restoring data using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      are
            relaxed; when one of these types of mismatches is
            encountered,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      does not stop
            with an error as it did previously, but rather accepts the
            data and inserts it into the target table while issuing a
            warning to the user that this is being done. This behavior
            occurs whether or not either of the options
      <code class="option">
       --skip-table-check
      </code>
      or
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_promote-attributes">
       <code class="option">
        --promote-attributes
       </code>
      </a>
      is
            in use. These differences in column definitions are of the
            following types:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         Different
         <code class="literal">
          COLUMN_FORMAT
         </code>
         settings
                (
         <code class="literal">
          FIXED
         </code>
         ,
         <code class="literal">
          DYNAMIC
         </code>
         ,
         <code class="literal">
          DEFAULT
         </code>
         )
        </p>
       </li>
       <li class="listitem">
        <p>
         Different
         <code class="literal">
          STORAGE
         </code>
         settings
                (
         <code class="literal">
          MEMORY
         </code>
         ,
         <code class="literal">
          DISK
         </code>
         )
        </p>
       </li>
       <li class="listitem">
        <p>
         Different default values
        </p>
       </li>
       <li class="listitem">
        <p>
         Different distribution key settings
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_skip-unknown-objects">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_skip-unknown-objects">
       <code class="option">
        --skip-unknown-objects
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098285984">
     </a>
     <a class="indexterm" name="idm46045098284528">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for skip-unknown-objects">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --skip-unknown-objects
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      This option causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      to ignore
            any schema objects it does not recognize while reading a
            native
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      backup. This can be
            used for restoring a backup made from a cluster running (for
            example) NDB 7.6 to a cluster running NDB Cluster 7.5.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_slice-id">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_slice-id">
       <code class="option">
        --slice-id
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098271808">
     </a>
     <a class="indexterm" name="idm46045098270320">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for slice-id">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --slice-id=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           1023
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      When restoring by slices, this is the ID of the slice to
            restore. This option is always used together with
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_num-slices">
       <code class="option">
        --num-slices
       </code>
      </a>
      , and its
            value must be always less than that of
      <code class="option">
       --num-slices
      </code>
      .
     </p>
     <p>
      For more information, see the description of the
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_num-slices">
       <code class="option">
        --num-slices
       </code>
      </a>
      elsewhere
            in this section.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_tab">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_tab">
       <code class="option">
        --tab
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        dir_name
       </code>
      </em>
      ,
      <code class="option">
       -T
      </code>
      <em class="replaceable">
       <code>
        dir_name
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098247184">
     </a>
     <a class="indexterm" name="idm46045098245696">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for tab">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --tab=path
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Directory name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Causes
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print-data">
       <code class="option">
        --print-data
       </code>
      </a>
      to
            create dump files, one per table, each named
      <code class="filename">
       <em class="replaceable">
        <code>
         tbl_name
        </code>
       </em>
       .txt
      </code>
      .
            It requires as its argument the path to the directory where
            the files should be saved; use
      <code class="literal">
       .
      </code>
      for the
            current directory.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_timestamp-printouts">
      </a>
      <code class="option">
       --timestamp-printouts
      </code>
     </p>
     <a class="indexterm" name="idm46045098231680">
     </a>
     <a class="indexterm" name="idm46045098230224">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for timestamp-printouts">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --timestamp-printouts{=true|false}
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           true
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Causes info, error, and debug log messages to be prefixed
            with timestamps.
     </p>
     <p>
      This option is enabled by default. Disable it with
      <code class="option">
       --timestamp-printouts=false
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_usage">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_usage">
       <code class="option">
        --usage
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098214944">
     </a>
     <a class="indexterm" name="idm46045098213456">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for usage">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --usage
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Display help text and exit; same as
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_help">
       <code class="option">
        --help
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_verbose">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_verbose">
       <code class="option">
        --verbose
       </code>
      </a>
      =
      <em class="replaceable">
       <code>
        #
       </code>
      </em>
     </p>
     <a class="indexterm" name="idm46045098202352">
     </a>
     <a class="indexterm" name="idm46045098200864">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for verbose">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --verbose=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           255
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Sets the level for the verbosity of the output. The minimum
            is 0; the maximum is 255. The default value is 1.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_version">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_version">
       <code class="option">
        --version
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098181792">
     </a>
     <a class="indexterm" name="idm46045098180304">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for version">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --version
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Display version information and exit.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_ndb_restore_with-apply-status">
      </a>
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_with-apply-status">
       <code class="option">
        --with-apply-status
       </code>
      </a>
     </p>
     <a class="indexterm" name="idm46045098170544">
     </a>
     <a class="indexterm" name="idm46045098169088">
     </a>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for with-apply-status">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --with-apply-status
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <p>
      Restore all rows from the backup's
      <code class="literal">
       ndb_apply_status
      </code>
      table (except for the
            row having
      <code class="literal">
       server_id = 0
      </code>
      , which is
            generated using
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-epoch">
       <code class="option">
        --restore-epoch
       </code>
      </a>
      ). This
            option requires that
      <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-data">
       <code class="option">
        --restore-data
       </code>
      </a>
      also be
            used.
     </p>
     <p>
      If the
      <code class="literal">
       ndb_apply_status
      </code>
      table from the
            backup already contains a row with
      <code class="literal">
       server_id =
            0
      </code>
      ,
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <code class="option">
       --with-apply-status
      </code>
      deletes it. For this
            reason, we recommend that you use
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <code class="option">
       --restore-epoch
      </code>
      after invoking
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      with the
      <code class="option">
       --with-apply-status
      </code>
      option. You can also
            use
      <code class="option">
       --restore-epoch
      </code>
      concurrently with the
            last of any invocations of
      <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
       <span class="command">
        <strong>
         ndb_restore
        </strong>
       </span>
      </a>
      <code class="option">
       --with-apply-status
      </code>
      used to restore the
            cluster.
     </p>
     <p>
      For more information, see
      <a class="xref" href="mysql-cluster-replication-schema.html#ndb-replication-ndb-apply-status" title="ndb_apply_status Table">
       ndb_apply_status Table
      </a>
      .
     </p>
    </li>
   </ul>
  </div>
  <a class="indexterm" name="idm46045098147232">
  </a>
  <p>
   Typical options for this utility are shown here:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa15171218"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">ndb_restore <span class="token punctuation">[</span><span class="token property">-c</span> <em class="replaceable">connection_string</em><span class="token punctuation">]</span> <span class="token property">-n</span> <em class="replaceable">node_id</em> <span class="token property">-b</span> <em class="replaceable">backup_id</em> \
      <span class="token punctuation">[</span><span class="token property">-m</span><span class="token punctuation">]</span> <span class="token property">-r</span> <span class="token constant">--backup-path</span><span class="token attr-value"><span class="token punctuation">=</span><em class="replaceable">/path/to/backup/files</em></span></code></pre>
  </div>
  <p>
   Normally, when restoring from an NDB Cluster backup,
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   requires at a minimum the
   <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid">
    <code class="option">
     --nodeid
    </code>
   </a>
   (short form:
   <code class="option">
    -n
   </code>
   ),
   <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid">
    <code class="option">
     --backupid
    </code>
   </a>
   (short form:
   <code class="option">
    -b
   </code>
   ), and
   <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-path">
    <code class="option">
     --backup-path
    </code>
   </a>
   options.
  </p>
  <p>
   The
   <code class="option">
    -c
   </code>
   option is used to specify a connection
        string which tells
   <code class="literal">
    ndb_restore
   </code>
   where to
        locate the cluster management server (see
   <a class="xref" href="mysql-cluster-connection-strings.html" title="25.4.3.3 NDB Cluster Connection Strings">
    Section 25.4.3.3, “NDB Cluster Connection Strings”
   </a>
   ). If this
        option is not used, then
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   attempts
        to connect to a management server on
   <code class="literal">
    localhost:1186
   </code>
   . This utility acts as a
        cluster API node, and so requires a free connection
   <span class="quote">
    “
    <span class="quote">
     slot
    </span>
    ”
   </span>
   to connect to the cluster management server.
        This means that there must be at least one
   <code class="literal">
    [api]
   </code>
   or
   <code class="literal">
    [mysqld]
   </code>
   section
        that can be used by it in the cluster
   <code class="filename">
    config.ini
   </code>
   file. It is a good idea to keep
        at least one empty
   <code class="literal">
    [api]
   </code>
   or
   <code class="literal">
    [mysqld]
   </code>
   section in
   <code class="filename">
    config.ini
   </code>
   that is not being used for a
        MySQL server or other application for this reason (see
   <a class="xref" href="mysql-cluster-api-definition.html" title="25.4.3.7 Defining SQL and Other API Nodes in an NDB Cluster">
    Section 25.4.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”
   </a>
   ).
  </p>
  <p>
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   can decrypt an encrypted backup
        using
   <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_decrypt">
    <code class="option">
     --decrypt
    </code>
   </a>
   and
   <a class="link" href="mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backup-password">
    <code class="option">
     --backup-password
    </code>
   </a>
   . Both
        options must be specified to perform decryption. See the
        documentation for the
   <a class="link" href="mysql-cluster-backup-using-management-client.html" title="25.6.8.2 Using The NDB Cluster Management Client to Create a Backup">
    <code class="literal">
     START
        BACKUP
    </code>
   </a>
   management client command for information on
        creating encrypted backups.
  </p>
  <p>
   You can verify that
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   is connected
        to the cluster by using the
   <a class="link" href="mysql-cluster-mgm-client-commands.html#ndbclient-show">
    <code class="literal">
     SHOW
    </code>
   </a>
   command in the
   <a class="link" href="mysql-cluster-programs-ndb-mgm.html" title="25.5.5 ndb_mgm — The NDB Cluster Management Client">
    <span class="command">
     <strong>
      ndb_mgm
     </strong>
    </span>
   </a>
   management client. You can also
        accomplish this from a system shell, as shown here:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa62397107"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal"><span class="token prompt">$&gt; </span><span class="token command">ndb_mgm</span> <span class="token property">-e</span> <span class="token atrule">"SHOW"</span></code></pre>
  </div>
  <p>
   <b>
    Error reporting.
   </b>
   <a class="indexterm" name="idm46045098114896">
   </a>
   <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
    <span class="command">
     <strong>
      ndb_restore
     </strong>
    </span>
   </a>
   reports both temporary and
          permanent errors. In the case of temporary errors, it may able
          to recover from them, and reports
   <code class="literal">
    Restore successful,
          but encountered temporary error, please look at
          configuration
   </code>
   in such cases.
  </p>
  <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Important
   </div>
   <p>
    After using
    <a class="link" href="mysql-cluster-programs-ndb-restore.html" title="25.5.23 ndb_restore — Restore an NDB Cluster Backup">
     <span class="command">
      <strong>
       ndb_restore
      </strong>
     </span>
    </a>
    to initialize an
          NDB Cluster for use in circular replication, binary logs on
          the SQL node acting as the replica are not automatically
          created, and you must cause them to be created manually. To
          cause the binary logs to be created, issue a
    <a class="link" href="show-tables.html" title="15.7.7.39 SHOW TABLES Statement">
     <code class="literal">
      SHOW TABLES
     </code>
    </a>
    statement on that
          SQL node before running
    <a class="link" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
     <code class="literal">
      START
          REPLICA
     </code>
    </a>
    . This is a known issue in NDB Cluster.
   </p>
  </div>
 </div>
 <br/>
</div>
