Oracle 5.0 Reference Manual page 1659

ndb_restore
completion of a backup. (See
Create a Backup".)
Important
When restoring cluster backups, you must be sure to restore all data nodes
from backups having the same backup ID. Using files from different backups
will at best result in restoring the cluster to an inconsistent state, and may fail
altogether.
The path to the backup directory is required; this is supplied to
option, and must include the subdirectory corresponding to the ID backup of the backup
backup_path
to be restored. For example, if the data node's
backup directory is /var/lib/mysql-cluster/BACKUP, and the backup files for the backup
with the ID 3 can be found in /var/lib/mysql-cluster/BACKUP/BACKUP-3. The path may be
absolute or relative to the directory in which the
optionally prefixed with backup_path=.
Note
Previous to MySQL 5.0.38, the path to the backup directory was specified as
shown here, with
[backup_path=]/path/to/backup/files
Beginning with MySQL 5.0.38, this syntax changed to
path/to/backup/files, to conform more closely with options used by other
MySQL programs;
option.
It is possible to restore a backup to a database with a different configuration than it was created from.
For example, suppose that a backup with backup ID 12, created in a cluster with two database nodes
having the node IDs
2
be run twice—once for each database node in the cluster where the backup was taken. However,
cannot always restore backups made from a cluster running one version of MySQL to a
ndb_restore
cluster running a different MySQL version. See
Cluster", for more information.
Important
It is not possible to restore a backup made from a newer version of MySQL
Cluster using an older version of ndb_restore. You can restore a backup
made from a newer version of MySQL to an older cluster, but you must use a
copy of
For example, to restore a cluster backup taken from a cluster running MySQL
5.0.45 to a cluster running MySQL Cluster 5.0.41, you must use a copy of
ndb_restore
For more rapid restoration, the data may be restored in parallel, provided that there is a sufficient
number of cluster connections available. That is, when restoring to multiple nodes in parallel, you must
have an or
[api] [mysqld]
process. However, the data files must always be applied before the logs.
ndb_restore
--dont_ignore_systab_0
Normally, when restoring table data and metadata,
table that is present in the backup.
restored. This option is intended for experimental and development use only, and is not recommended
in a production environment.
— Restore a MySQL Cluster Backup
Section 17.5.3.2, "Using The MySQL Cluster Management Client to
backup_path=
--backup_id
and 3, is to be restored to a cluster with four nodes. Then
from the newer MySQL Cluster version to do so.
ndb_restore
from the 5.0.45 distribution.
section in the cluster
--dont_ignore_systab_0
1639
ndb_restore
is /var/lib/mysql-cluster, then the
DataDir
executable is located, and may be
ndb_restore
being optional:
is required, and there is no short form for this
Section 17.2.6, "Upgrading and Downgrading MySQL
file available for each concurrent
config.ini
ignores the copy of the
ndb_restore
causes the system table to be
using the
--
--backup_path=/
ndb_restore
system
NDB
must