16.6.5.2. Using The Management Server to Create a Backup
Before starting a backup, make sure that the cluster is
properly configured for performing one. (See
Section 16.6.5.4, “Configuration for Cluster Backup”.)
Creating a backup using the management server involves the
following steps:
Start the management server (ndb_mgm).
Execute the command START BACKUP.
The management server will reply with the message
Start of backup ordered. This means
that the management server has submitted the request to
the cluster, but has not yet received any response.
The management server will reply Backup
backup_id started,
where backup_id is the unique
identifier for this particular backup. (This identifier
will also be saved in the cluster log, if it has not been
configured otherwise.) This means that the cluster has
received and processed the backup request. It does
not mean that the backup has
finished.
The management server will signal that the backup is
finished with the message Backup
backup_id completed.
To abort a backup that is already in progress:
Start the management server.
Execute the command ABORT BACKUP
backup_id. The number
backup_id is the identifier of
the backup that was included in the response of the
management server when the backup was started (in the
message Backup
backup_id started).
The management server will acknowledge the abort request
with Abort of backup
backup_id ordered;
note that it has received no actual response to this
request yet.
After the backup has been aborted, the management server
will report Backup
backup_id has been aborted for
reason XYZ. This
means that the cluster has terminated the backup and that
all files related to this backup have been removed from
the cluster filesystem.
It is also possible to abort a backup in progress from the
system shell using this command:
shell> ndb_mgm -e "ABORT BACKUP backup_id"
Note: If there is no backup
with ID backup_id running when it
is aborted, the management server makes no explicit response.
However, the fact that an invalid abort command was sent is
indicated in the cluster log.
