Oracle 5.0 Reference Manual page 1679

The
Backup backup_id started from node management_node_id has been aborted
messages mean that the backup has been terminated and that all files relating to this backup have
been removed from the cluster file system.
It is also possible to abort a backup in progress from a system shell using this command:
shell> ndb_mgm -e "ABORT BACKUP backup_id"
17.5.3.3. Configuration for MySQL Cluster Backups
Five configuration parameters are essential for backup:
•
BackupDataBufferSize
The amount of memory used to buffer data before it is written to disk.
•
BackupLogBufferSize
The amount of memory used to buffer log records before these are written to disk.
•
BackupMemory
The total memory allocated in a database node for backups. This should be the sum of the memory
allocated for the backup data buffer and the backup log buffer.
•
BackupWriteSize
The default size of blocks written to disk. This applies for both the backup data buffer and the backup
log buffer.
•
BackupMaxWriteSize
The maximum size of blocks written to disk. This applies for both the backup data buffer and the
backup log buffer.
More detailed information about these parameters can be found in
17.5.3.4. MySQL Cluster Backup Troubleshooting
If an error code is returned when issuing a backup request, the most likely cause is insufficient memory
or disk space. You should check that there is enough memory allocated for the backup.
You should also make sure that there is sufficient space on the hard drive partition of the backup
target.
Online Backup of MySQL Cluster
Note
If there is no backup having the ID
is issued, the management client makes no response, nor is it indicated
BACKUP
in the cluster log that an invalid abort command was sent.
Important
If you have set
BackupDataBufferSize
their sum is greater than 4MB, then you must also set
See [1581].
BackupMemory
backup_id
and
BackupLogBufferSize
1659
running when an
ABORT
Backup Parameters.
BackupMemory
and
as well.