MySQL Cluster Tutorial - cdn.oreillystatic.com

• Stored routines and other none table metadata is not stored in Cluster and consequently
not backed up the online backup tool.
• Going from one version of MySQL Cluster to another might bring incompatible table
formats.
For example:
shell> mysqldump --no-data --routines --all-tablespaces --all-databases >
meta_backup.sql
Restoring using ndb_restore
Backups made using ndb_mgm’s START BACKUP command can be restored using
ndb_restore. For this to work, you’ll need to configure your MySQL Cluster so there is
always a free [API] slot, which can connect from a dedicated machine which will do the
restore.
Note that MySQL Cluster needs to be empty before restoring data. There is a possibility
using ndb_restore to only recover a selection of tables. This could be used for restoring a
table which was dropped by mistake.
Since backups are moved away from the data nodes ones they are made, ndb_restore will
not necessary run from the data nodes. For simplicity, this tutorial assumes they were kept
in place.
Restoring meta data
Meta data can be restored by both using ndb_restore and the mysql client tool. However, it
is advised to restore the backups done with the mysqldump tool.
For example using an SQL dump of the meta data:
shell> mysql -uroot < meta_backup.sql
However, it’s also important to know how to do it using ndb_restore. Suppose you have
the following backup with ID 2 and need to restore Node 3 and Node 4, which were started
empty.
BACKUP-2-0.3.Data
BACKUP-2-0.4.Data
BACKUP-2.3.ctl
BACKUP-2.3.log
BACKUP-2.4.ctl
BACKUP-2.4.log
When you use ndb_restore, you only need restore the meta once. Every backup of each
node contains this information, so it doesn’t matter which one you take.
Lets restore the meta data using the backup of Node 3:
shell> ndb_restore -m -b 2 -n 3 /path/to/BACKUP-2/
-m = restore meta
-b = backup ID
-n = node ID
The tables should now already be available.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 37/81