Command-Line Format --remap-column=[db].[tbl].[col]:[fn]: [args] Introduced 8.0.21-ndb-8.0.21 Type String Default Value [none] ndb_restore — Restore an NDB Cluster Backup which LCPs are performed ( MaxDiskWriteSpeed  and related parameters), in order to free space more quickly. • --remap-column= db . tbl . col : fn : args • db : Database name, following any renames performed by  --rewrite-database . • tbl : Table name. • col : Name of the column to be updated. This column must be of type  INT  or  BIGINT . The column can also be but is not required to be  UNSIGNED . • fn : Function name; currently, the only supported name is  offset . • args : Arguments supplied to the function. Currently, only a single argument, the size of the offset to be added by the  offset  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  col  is an  INT column, then the allowed range of the argument passed to the  offset  function is  -2147483648 to  2147483647  (see Section 11.1.2, “Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT” ). shell>  ndb_restore --restore-data --remap-column=hr.employee.salary:offset:10000 \ shell>  ndb_restore --restore-data --remap-column=hr.employee.id:offset:1000 \ --remap-column=hr.manager.id:offset:1000 --remap-column=hr.firstaiders.id:offset:1000 4388 --remap-column  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: (Other options not shown here may also be used.) 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 Section 23.5.8.2, “Using The NDB Cluster Management Client to Create a Backup” ) and ndb_restore  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  ndb_restore  to remap columns of different tables, as shown here: 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  BIGINT , and the option attempts to apply an offset value of 8 on a row in which the column value is 4294967291, since  4294967291 + 8 = 4294967299 > 4294967295 . When used together with  --restore-data , this option applies a function to the value of the indicated column. Values in the argument string are listed here: