Movatterモバイル変換

Back up allNDB databases in the cluster, using theSTART BACKUP command in thendb_mgm client (seeSection 25.6.8, “Online Backup of NDB Cluster”).

At some later point, prior to restoring the cluster, make a backup of themysql.ndb_binlog_index table. It is probably simplest to usemysqldump for this task. Also back up the binary log files at this time.

This backup should be updated regularly—perhaps even hourly—depending on your needs.

(Catastrophic failure or error occurs.)

Locate the last known good backup.

Clear the data node file systems (usingndbd--initial orndbmtd--initial).

UseDROP TABLE orTRUNCATE TABLE with themysql.ndb_binlog_index table.

Executendb_restore, restoring all data. You must include the--restore-epoch option when you runndb_restore, so that thendb_apply_status table is populated correctly. (SeeSection 25.5.23, “ndb_restore — Restore an NDB Cluster Backup”, for more information.)

Restore thendb_binlog_index table from the output ofmysqldump and restore the binary log files from backup, if necessary.

Find the epoch applied most recently—that is, the maximumepoch column value in thendb_apply_status table—as the user variable@LATEST_EPOCH (emphasized):

SELECT@LATEST_EPOCH:=MAX(epoch)    FROM mysql.ndb_apply_status;

Find the latest binary log file (@FIRST_FILE) and position (Position column value) within this file that correspond to@LATEST_EPOCH in thendb_binlog_index table:

SELECT Position,@FIRST_FILE:=File    FROM mysql.ndb_binlog_index    WHERE epoch >@LATEST_EPOCH ORDER BY epoch ASC LIMIT 1;

Usingmysqlbinlog, replay the binary log events from the given file and position up to the point of the failure. (SeeSection 6.6.9, “mysqlbinlog — Utility for Processing Binary Log Files”.)