Author: jstephens
Date: 2007-04-13 12:07:40 +0200 (Fri, 13 Apr 2007)
New Revision: 5870
Log:
-e option must be used when restoring a backup for cluster replication
(Thanks, Jeb!)
Modified:
trunk/refman-5.1/mysql-cluster.xml
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-04-13 09:40:22 UTC (rev 5869)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-04-13 10:07:40 UTC (rev 5870)
Changed blocks: 4, Lines Added: 30, Lines Deleted: 12; 3845 bytes
@@ -13318,8 +13318,7 @@
</para>
<programlisting>
-ndb_restore [-c <replaceable>connectstring</replaceable>] -n
-<replaceable>node_id</replaceable> [-s] [-m] -b
<replaceable>backup_id</replaceable> -r
[backup_path=]<replaceable>/path/to/backup/files</replaceable>
+ndb_restore [-c <replaceable>connectstring</replaceable>] -n
<replaceable>node_id</replaceable> [-s] [-m] -b
<replaceable>backup_id</replaceable> -r
[backup_path=]<replaceable>/path/to/backup/files</replaceable> [-e]
</programlisting>
<para>
@@ -13404,6 +13403,18 @@
message displayed upon completion of a backup. (See
<xref linkend="mysql-cluster-backup-using-management-client"/>.)
</para>
+
+ <para>
+ <option>-e</option> adds (or restores) epoch information to
+ the cluster replication status table. This is useful for
+ starting replication on a MySQL Cluster replication slave.
+ When this option is used, the row in the
+ <literal>mysql.ndb_apply_status</literal> having
+ <literal>0</literal> in the <literal>id</literal>
column is
+ updated if it already exists; such a row is inserted if it
+ does not already exist. (See
+ <xref linkend="mysql-cluster-replication-backups"/>.)
+ </para>
<para>
The path to the backup directory is required, and must
@@ -13524,7 +13535,7 @@
<entry><option>-f</option></entry>
<entry>Do not ignore system table during restore —
<emphasis>EXPERIMENTAL; not for production
- use</emphasis></entry>
+ use</emphasis></entry>
<entry><literal>FALSE</literal></entry>
</row>
<row>
@@ -18289,20 +18300,27 @@
<programlisting>
shell<replaceable>S</replaceable>> <userinput>ndb_restore -c
rep-slave:1186 -n 2 -b 1 -m \</userinput>
- <userinput>-r ./VAR/BACKUPS/BACKUP-1</userinput>
+ <userinput>-r ./var/BACKUPS/BACKUP-1</userinput>
shell<replaceable>S</replaceable>> <userinput>ndb_restore -c
rep-slave:1186 -n 3 -b 1 \</userinput>
- <userinput>-r ./VAR/BACKUPS/BACKUP-1</userinput>
+ <userinput>-r ./var/BACKUPS/BACKUP-1</userinput>
shell<replaceable>S</replaceable>> <userinput>ndb_restore -c
rep-slave:1186 -n 4 -b 1 \</userinput>
- <userinput>-r ./VAR/BACKUPS/BACKUP-1</userinput>
+ <userinput>-r ./var/BACKUPS/BACKUP-1</userinput>
shell<replaceable>S</replaceable>> <userinput>ndb_restore -c
rep-slave:1186 -n 5 -b 1 -e \</userinput>
- <userinput>-r ./VAR/BACKUPS/BACKUP-1</userinput>
+ <userinput>-r ./var/BACKUPS/BACKUP-1</userinput>
</programlisting>
- <para>
- This sequence of commands causes the most recent epoch
- records to be written to the slave's
- <literal>ndb_apply_status</literal> table.
- </para>
+ <important>
+ <para>
+ The <option>-e</option> (or
+ <option>--restore-epoch</option>) option in the final
+ invocation of <command>ndb_restore</command> in this
+ example is required in order that the epoch is written to
+ the slave <literal>mysql.ndb_apply_status</literal>.
+ Without this information, the slave will not be able to
+ synchronize properly with the master. (See
+ <xref linkend="mysql-cluster-restore"/>.)
+ </para>
+ </important>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5870 - trunk/refman-5.1 | jon | 13 Apr |