The "start backup" command seems to have worked for me. All files were created
as described on pages 41-43 of the MySQL Cluster Administration Guide.
Any advice on the restore command syntax?
I've read the guide [p. 42 "How to restore a backup"] and checked out the
helpful screenshot that shows:
BACKUP-12> restore -backupid 12 -nodeid 2 -restore -restore_meta
Seems that the command name has changed to ndb_restore.
[root@BOX2 BACKUP-1]# ndb_restore
Usage: ndb_restore [--connect="nodeid=<api id>;host=<hostname:port>"]
[-c "nodeid=<api id>;host=<hostname:port>"] [--nodeid=db node id]
[-n db node id] [--backupid=backup id] [-b backup id] [--print]
[--print_data] [--print_meta] [--print_log] [--restore_data] [-r]
[--restore_meta] [-m] [--parallelism=Parallelism] [-p Parallelism]
[--dont_ignore_systab_0] [-f] <path to backup files>
Can't get the command to work. It's in my path. Seems like I have the syntax
[root@BOX2 BACKUP-1]# ndb_restore --backupid=1 --nodeid=2 --restore_data
I'm running it from a directory with the backup files and an Ndb.cfg file.
Also tried it with the --connect string:
[root@cooler BACKUP-1]# ndb_restore --connect "nodeid=11;host=<mazda:2200>"
--backupid=1 --nodeid=2 --restore_data --restore_metadata --print_log
Any advice on command syntax?
--- Jonas Oreland <jonas.oreland@stripped> wrote:
> Joseph E. Sacco, Ph.D. wrote:
> > Question:
> > Does Backup work [yet]?
> Yes, it should work.
> But it seems like a bug has been introduced lately.
> Please file a bug report,
> and I will look at this tonight or tomorrow morning...
> > I tried to run a backup of a two replica, two db node, two computer
> > cluster built from the 5Aug04 code, patch level 1.1953.
> cool: that the latest changeset for me aswell, talk about bleeding edge.
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe: http://lists.mysql.com/cluster?unsub=1
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.