Oracle 5.0 Reference Manual page 1677

A log file containing records of committed transactions. Only transactions on tables stored in the
backup are stored in the log. Nodes involved in the backup save different records because different
nodes host different database fragments.
In the listing above,
for the node creating the file.
17.5.3.2. Using The MySQL Cluster Management Client to Create a Backup
Before starting a backup, make sure that the cluster is properly configured for performing one. (See
Section 17.5.3.3, "Configuration for MySQL Cluster
The
START BACKUP
START BACKUP [backup_id] [wait_option]
wait_option:
WAIT {STARTED | COMPLETED} | NOWAIT
Successive backups are automatically identified sequentially, so the backup_id, an integer greater
than or equal to 1, is optional; if it is omitted, the next available value is used. If an existing
value is used, the backup fails with the error
backup_id
The maximum supported value for
The
wait_option
a
START BACKUP
•
•
•
WAIT COMPLETED
The procedure for creating a backup consists of the following steps:
1. Start the management client (ndb_mgm), if it not running already.
2. Execute the
progress of the backup, as shown here:
ndb_mgm>
Waiting for completed, this may take several minutes
Node 2: Backup 1 started from node 1
Node 2: Backup 1 started from node 1 completed
StartGCP: 177 StopGCP: 180
#Records: 7362 #LogRecords: 0
Data: 453648 bytes Log: 0 bytes
ndb_mgm>
3.
4. The management client indicates with a message like this one that the backup has started:
Backup backup_id
As is the case for the notification that the backup has started,
for this particular backup, and
coordinating the backup with the data nodes. This output is accompanied by additional information
Online Backup of MySQL Cluster
stands for the backup identifier and
backup_id
command is used to create a backup:
must follow
START BACKUP
backup_id
Note
If you start a backup using
is required.
can be used to determine when control is returned to the management client after
command is issued, as shown in the following list:
is the default.
command. This produces several lines of output indicating the
START BACKUP
START BACKUP
started from node
node_id
Backups".)
Backup failed: file already
immediately, before any other options are used.
in MySQL 5.0 is 2147483648 (2
ndb_mgm -e "START
node_id completed
is the node ID of the management server that is
1657
is the unique identifier
node_id
exists. If used, the
31
). (Bug #43042)
BACKUP", the
backup_id
is the unique identifier
backup_id
backup_id