ndb_restore — Restore an NDB Cluster Backup now 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. When using this option in NDB 8.0.16 or later, it is recommended that auto synchronization be disabled by setting  ndb_metadata_check=OFF  until  ndb_restore  has completed restoring the metadata, after which it can it turned on again to synchronize objects newly created in the NDB dictionary. The cluster should have an empty database when starting to restore a backup. (In other words, you should start the data nodes with  --initial  prior to performing the restore.) ndb_restore  does not by default restore distributed MySQL privilege tables created in releases of NDB Cluster prior to version 8.0, which does not support distrubuted privileges as implemented in NDB 7.6 and earlier. This option causes  ndb_restore  to restore them. In NDB 8.0.16 and later, such tables are not used for access control; as part of the MySQL server’s upgrade process, the server creates  InnoDB  copies of these tables local to itself. For more information, see Section 23.2.7, “Upgrading and Downgrading NDB Cluster” , as well as Section 6.2.3, “Grant Tables” . 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  products , you can restore the data it contains to a database named  inventory , use this option as shown here (omitting any other options that might be required): shell> ndb_restore --rewrite-database=product,inventory The option can be employed multiple times in a single invocation of  ndb_restore . Thus it is possible to restore simultaneously from a database named  db1  to a database named  db2  and from a database named  db3  to one named  db4  using  --rewrite-database=db1,db2 --rewrite- database=db3,db4 . Other  ndb_restore  options may be used between multiple occurrences of  -- rewrite-database . In the event of conflicts between multiple  --rewrite-database  options, the last  --rewrite- database  option used, reading from left to right, is the one that takes effect. For example, if  -- rewrite-database=db1,db2 --rewrite-database=db1,db3  is used, only  --rewrite- database=db1,db3  is honored, and  --rewrite-database=db1,db2  is ignored. It is also possible to restore from multiple databases to a single database, so that  --rewrite-database=db1,db3 -- 4390 • --rewrite-database = olddb,newdb • --restore-privilege-tables Note Command-Line Format --restore-privilege-tables Deprecated 8.0.16-ndb-8.0.16 Type Boolean Default Value FALSE  (If option is not used) Command-Line Format --rewrite-database=olddb,newdb Type String Default Value none