Bug #42880 Wrong syntax for ndb_restore for --backup_path
Submitted: 16 Feb 2009 12:41 Modified: 17 Feb 2009 16:36
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:ALL OS:Any
Assigned to: Jon Stephens CPU Architecture:Any

[16 Feb 2009 12:41] Geert Vanderkelen
Description:
Following URL:
 http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-restore.html

The line with ndb_restore options:
 ndb_restore [-c connectstring] -n node_id [-s] [-m] -b backup_id -r [backup_path=]/path/to/backup/files [-e]

[backup_path] should be [--backup_path]

Otherwise it thinks it's part of the file.

How to repeat:
shell> ndb_restore -n 4 -b 1 -m -r backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Nodeid = 4
Backup Id = 1
backup path = backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Opening file 'backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/BACKUP-1.4.ctl'
Progress reporting degraded output since fstat failed,errno: 9
Failed to read backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/BACKUP-1.4.ctl

Correct version:

shell> ndb_restore -n 4 -b 1 -m -r --backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Nodeid = 4
Backup Id = 1
backup path = /data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Opening file '/data2/users/geert/cluster/master/BACKUP/BACKUP-1/BACKUP-1.4.ctl'
Backup version in files: ndb-6.3.11 ndb version: mysql-5.1.31 ndb-6.3.22

Suggested fix:
Small update in the docs.
[16 Feb 2009 12:46] Jon Stephens
It's a Docs bug, so I've changed the Category and Lead to match.
[17 Feb 2009 16:36] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

NOTE: The syntax changed in 5.0.38/5.1.17/NDB-6.1.7 (but not in 4.1.X) to conform better with how other MySQL program options work. I've updated the documentation accordingly.