ndb_restore — Restore an NDB Cluster Backup Format Description Added, Deprecated, or Removed -? --verbose=# Level of verbosity in output (Supported in all NDB releases based on MySQL 8.0) --version , -V Display version information and exit (Supported in all NDB releases based on MySQL 8.0) • --allow-pk-changes Command-Line Format --allow-pk-changes[=0|1] Introduced 8.0.21-ndb-8.0.21 Type Integer Default Value 0 Minimum Value 0 Maximum Value 1 When this option is set to  1 ,  ndb_restore  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 mor efficient than issuing many  ALTER TABLE statements after restoring table schemas and data. The following changes in primary key definitions are supported by  --allow-pk-changes : • Extending the primary key : A non-nullable column that exists in the table schema in the backup becomes part of the table’s primary key in the database. • Contracting the primary key (1) : 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. • Contracting the primary key (2) : A column that is already part of the table’s primary key in the backup schema is removed from the table entirely. 1. Restore table schemas using  ndb_restore --restore-meta 2. Alter schema to that desired, or create it 4370 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  ndb_restore  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  --ignore-extended-pk-updates  option; see the description of this option for more information. These differences can be combined with other schema differences supported by  ndb_restore , including changes to blob and text columns requiring the use of staging tables. Basic steps in a typical scenario using primary key schema changes are listed here: Important