![background image](http://html1.mh-extra.com/html/oracle/5-0/5-0_reference-manual_16461961676.webp)
Online Backup of MySQL Cluster
1656
In addition to the central configuration file, a cluster may also be controlled through a command-
line interface available through the management client
ndb_mgm
. This is the primary administrative
interface to a running cluster.
Commands for the event logs are given in
Section 17.5.6, “Event Reports Generated in MySQL
Cluster”
; commands for creating backups and restoring from them are provided in
Section 17.5.3,
“Online Backup of MySQL Cluster”
.
The management client has the following basic commands. In the listing that follows,
node_id
denotes
either a database node ID or the keyword
ALL
, which indicates that the command should be applied to
all of the cluster's data nodes.
•
•
•
•
•
•
•
•
•
•
17.5.3. Online Backup of MySQL Cluster
The next few sections describe how to prepare for and then to create a MySQL Cluster backup using
the functionality for this purpose found in the
ndb_mgm
management client. To distinguish this type
of backup from a backup made using
mysqldump
, we sometimes refer to it as a “native” MySQL
Cluster backup. (For information about the creation of backups with
mysqldump
, see
Section 4.5.4,
“
mysqldump
— A Database Backup Program”
.) Restoration of MySQL Cluster backups is done
using the
ndb_restore
utility provided with the MySQL Cluster distribution; for information about
ndb_restore
and its use in restoring MySQL Cluster backups, see
Section 17.4.14, “
ndb_restore
— Restore a MySQL Cluster Backup”
.
17.5.3.1. MySQL Cluster Backup Concepts
A backup is a snapshot of the database at a given time. The backup consists of three main parts:
• Metadata.
The names and definitions of all database tables
• Table records.
The data actually stored in the database tables at the time that the backup was
made
• Transaction log.
A sequential record telling how and when data was stored in the database
Each of these parts is saved on all nodes participating in the backup. During backup, each node saves
these three parts into three files on disk:
•
BACKUP-backup_id.node_id.ctl
A control file containing control information and metadata. Each node saves the same table
definitions (for all tables in the cluster) to its own version of this file.
•
BACKUP-backup_id-0.node_id.data
A data file containing the table records, which are saved on a per-fragment basis. That is, different
nodes save different fragments during the backup. The file saved by each node starts with a header
that states the tables to which the records belong. Following the list of records there is a footer
containing a checksum for all records.
•
BACKUP-backup_id.node_id.log
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...