(mysql.info.gz) MySQL Cluster Restore
Info Catalog
(mysql.info.gz) MySQL Cluster Backup Using Management Server
(mysql.info.gz) MySQL Cluster Backup
(mysql.info.gz) MySQL Cluster Backup Configuration
16.5.4.3 How to Restore a Cluster Backup
........................................
The restore program is implemented as separate command line utility.
It reads the files created from the backup and inserts the stored
information into the database. The restore program has to be executed
once for each set of backup files, i.e. as many times as there were
database nodes running when the backup we created.
The first time you run the restore program you also need to restore the
meta data, i.e. create tables. The restore program acts as an API to
the cluster and therefore needs a free connection to connect to. This
can be verified with the `ndb_mgm' command SHOW. The switch `-c
<connectstring>' may be used to locate the MGM node (see MySQL
Cluster Connectstring for info on connectstrings). The backup files
must be present in the directory given as an argument to the restore
program. The backup can be restored to a database with a different
configuration than it was created from. For example, consider if a
backup (with id 12) created in a cluster with two database nodes (with
node id 2 and node id 3) that should be restored to a cluster with four
nodes. The restore program then has to be executed two times (one for
each database node in the cluster where the backup was taken) as
described in the box below.
Note: for rapid restore, the data may be restored in parallel (provided
that there are enough free API connections available). Note however
that the data files must always be applied before the logs.
Note: the cluster should have an empty database when starting to
restore a backup.
Info Catalog
(mysql.info.gz) MySQL Cluster Backup Using Management Server
(mysql.info.gz) MySQL Cluster Backup
(mysql.info.gz) MySQL Cluster Backup Configuration
automatically generated byinfo2html