ndb_restore — Restore an NDB Cluster Backup 3. Back up the desired schema 4. Run  ndb_restore --disable-indexes  using the backup from the previous step, to drop indexes and constraints 5. Run  ndb_restore --allow-pk-changes  (possibly along with  --ignore-extended-pk- updates ,  --disable-indexes , and possibly other options as needed) to restore all data 6. Run  ndb_restore --rebuild-indexes  using the backup made with the desired schema, to rebuild indexes and constraints When extending the primary key, it may be necessary for  ndb_restore  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  NDB$RESTORE_PK_MAPPING , and is created on each table requiring it; it can be shared, if necessary, by multiple instances of  ndb_restore  instances running in parallel. (Running  ndb_restore --rebuild-indexes  at the end of the restore process causes this index to be dropped.) When used with the  --tab  and  --print-data  options, this causes the data to be appended to any existing files having the same names. • --append • --backup-path = dir_name The path to the backup directory is required; this is supplied to  ndb_restore  using the  --backup- path  option, and must include the subdirectory corresponding to the ID backup of the backup to be restored. For example, if the data node’s  DataDir  is  /var/lib/mysql-cluster , then the backup directory is  /var/lib/mysql-cluster/BACKUP , and the backup files for the backup with the ID 3 can be found in  /var/lib/mysql-cluster/BACKUP/BACKUP-3 . The path may be absolute or relative to the directory in which the  ndb_restore  executable is located, and may be optionally prefixed with backup-path= . 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  12 , created in a cluster with two storage nodes having the node IDs  2  and  3 , is to be restored to a cluster with four nodes. Then  ndb_restore must be run twice—once for each storage node in the cluster where the backup was taken. However, ndb_restore  cannot always restore backups made from a cluster running one version of MySQL to a cluster running a different MySQL version. It is not possible to restore a backup made from a newer version of NDB Cluster using an older version of  ndb_restore . You can restore a backup made from Command-Line Format --append Command-Line Format --backup-path=dir_name Type Directory name Default Value ./ Important 4371