Oracle 5.0 Reference Manual page 1678

including relevant global checkpoints, the number of records backed up, and the size of the data, as
shown here:
Node 2: Backup 1 started from node 1 completed
StartGCP: 177 StopGCP: 180
#Records: 7362 #LogRecords: 0
Data: 453648 bytes Log: 0 bytes
It is also possible to perform a backup from the system shell by invoking
option, as shown in this example:
execute
shell> ndb_mgm -e "START BACKUP 6 WAIT COMPLETED"
When using
START BACKUP
Cluster backups are created by default in the
This can be overridden for one or more data nodes individually, or for all cluster data nodes in the
file using the
config.ini
Nodes. The backup files created for a backup with a given
named
BACKUP-backup_id
To abort a backup that is already in progress:
1. Start the management client.
2. Execute this command:
ndb_mgm> ABORT BACKUP backup_id
The number
backup_id
management client when the backup was started (in the message
from node management_node_id).
3. The management client will acknowledge the abort request with
ordered.
4. After the backup has been aborted, the management client will report this fact in a manner similar
to what is shown here:
Node 1: Backup 3 started from 5 has been aborted.
Error: 1321 - Backup aborted by user request: Permanent error: User defined error
Node 3: Backup 3 started from 5 has been aborted.
Error: 1323 - 1323: Permanent error: Internal error
Node 2: Backup 3 started from 5 has been aborted.
Error: 1323 - 1323: Permanent error: Internal error
Node 4: Backup 3 started from 5 has been aborted.
Error: 1323 - 1323: Permanent error: Internal error
In this example, we have shown sample output for a cluster with 4 data nodes, where the
sequence number of the backup to be aborted is 3, and the management node to which the cluster
management client is connected has the node ID 5. The first node to complete its part in aborting
the backup reports that the reason for the abort was due to a request by the user. (The remaining
nodes report that the backup was aborted due to an unspecified internal error.)
Online Backup of MySQL Cluster
in this way, you must specify the backup ID.
BackupDataDir
in the backup directory.
is the identifier of the backup that was included in the response of the
Note
At this point, the management client has not yet received a response from
the cluster data nodes to this request, and the backup has not yet actually
been aborted.
Note
There is no guarantee that the cluster nodes respond to an
command in any particular order.
1658
subdirectory of the
BACKUP
configuration parameter as discussed in
backup_id
Abort of backup backup_id
with the
ndb_mgm -e
on each data node.
DataDir
Identifying Data
are stored in a subdirectory
Backup backup_id started
ABORT BACKUP
or
--