Online Backup of MySQL Cluster
1658
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
ndb_mgm
with the
-e
or
--
execute
option, as shown in this example:
shell>
ndb_mgm -e "START BACKUP 6 WAIT COMPLETED"
When using
START BACKUP
in this way, you must specify the backup ID.
Cluster backups are created by default in the
BACKUP
subdirectory of the
DataDir
on each data node.
This can be overridden for one or more data nodes individually, or for all cluster data nodes in the
config.ini
file using the
BackupDataDir
configuration parameter as discussed in
Identifying Data
Nodes
. The backup files created for a backup with a given
backup_id
are stored in a subdirectory
named
BACKUP-backup_id
in the backup directory.
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
is the identifier of the backup that was included in the response of the
management client when the backup was started (in the message
Backup backup_id started
from node management_node_id
).
3. The management client will acknowledge the abort request with
Abort of backup backup_id
ordered
.
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.
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.)
Note
There is no guarantee that the cluster nodes respond to an
ABORT BACKUP
command in any particular order.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...