List:Commits« Previous MessageNext Message »
From:jon Date:May 13 2006 12:28am
Subject:svn commit - mysqldoc@docsrva: r2083 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-05-13 02:28:36 +0200 (Sat, 13 May 2006)
New Revision: 2083

Log:

You can't use ndb_restore to backup/restore 5.1->5.0.

(Fixes Docs Bug #19489.)



Modified:
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.1/ndbcluster.xml

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-05-12 23:40:12 UTC (rev 2082)
+++ trunk/refman-4.1/ndbcluster.xml	2006-05-13 00:28:36 UTC (rev 2083)
@@ -9206,7 +9206,11 @@
           restored to a cluster with four nodes. Then
           <command>ndb_restore</command> must be run twice &mdash; once
           for each database node in the cluster where the backup was
-          taken.
+          taken. However, <command>ndb_restore</command> cannot always
+          restore backups made from a cluster running one version of
+          MySQL to a cluster running a different MySQL version. See  
+          <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
+          for more information.
         </para>
 
         <para>

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-05-12 23:40:12 UTC (rev 2082)
+++ trunk/refman-5.0/ndbcluster.xml	2006-05-13 00:28:36 UTC (rev 2083)
@@ -7958,6 +7958,13 @@
             Cluster downgrades from 5.0.12 to 5.0.11 (or earlier) are
             not supported.
           </para>
+          
+          <para>
+            You cannot restore with <command>ndb_restore</command> to a
+            MySQL 5.0 Cluster using a backup made from a Cluster running
+            MySQL 5.1. You must use <command>mysqldump</command> in such
+            cases. 
+          </para>
         </listitem>
 
         <listitem>
@@ -9847,7 +9854,11 @@
           restored to a cluster with four nodes. Then
           <command>ndb_restore</command> must be run twice &mdash; once
           for each database node in the cluster where the backup was
-          taken.
+          taken. However, <command>ndb_restore</command> cannot always
+          restore backups made from a cluster running one version of
+          MySQL to a cluster running a different MySQL version. See  
+          <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
+          for more information.
         </para>
 
         <para>

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-05-12 23:40:12 UTC (rev 2082)
+++ trunk/refman-5.1/ndbcluster.xml	2006-05-13 00:28:36 UTC (rev 2083)
@@ -6950,6 +6950,13 @@
             Cluster downgrades from 5.0.12 to 5.0.11 (or earlier) are
             not supported.
           </para>
+          
+          <para>
+            You cannot restore with <command>ndb_restore</command> to a
+            MySQL 5.0 Cluster using a backup made from a Cluster running
+            MySQL 5.1. You must use <command>mysqldump</command> in such
+            cases. 
+          </para>
         </listitem>
 
         <listitem>
@@ -9835,7 +9842,11 @@
           restored to a cluster with four nodes. Then
           <command>ndb_restore</command> must be run twice &mdash; once
           for each database node in the cluster where the backup was
-          taken.
+          taken. However, <command>ndb_restore</command> cannot always
+          restore backups made from a cluster running one version of
+          MySQL to a cluster running a different MySQL version. See  
+          <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
+          for more information.
         </para>
 
         <para>

Thread
svn commit - mysqldoc@docsrva: r2083 - in trunk: refman-4.1 refman-5.0 refman-5.1jon13 May