content_image/785082.jpg content_image/785083.jpg content_image/785084.jpg content_image/785085.jpg content_image/785086.jpg
<img src='content_image/785082.jpg'>

Cause ndb_restore  to output its log to stdout . 

• --print-meta 

<img src='content_image/785083.jpg'>

Print all metadata to stdout . 

• print-sql-log 

<img src='content_image/785084.jpg'>

Log SQL statements to stdout . 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 NDB  cannot be converted to valid SQL. 

This option does not work with tables having BLOB  columns. 

• --progress-frequency = N 

<img src='content_image/785085.jpg'>

Print a status report each N  seconds while the backup is in progress. 0 (the default) causes no status reports to be printed. The maximum is 65535. 

• --promote-attributes , -A 

<img src='content_image/785086.jpg'>

ndb_restore  supports limited attribute promotion  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 “larger, similar”  type. For example, data from a CHAR(20)  column can be restored to a column declared as VARCHAR(20) , VARCHAR(30) , or CHAR(30) ; data from a MEDIUMINT  column can be 

