svn commit - mysqldoc@docsrva: r6787 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-06-13 23:22:20 +0200 (Wed, 13 Jun 2007)
New Revision: 6787

Log:

Documented backup reporting enhancements for telco-6.2.2.



Modified:
   trunk/refman-5.1/mysql-cluster.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-06-13 20:12:36 UTC (rev 6786)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-06-13 21:22:20 UTC (rev 6787)
Changed blocks: 3, Lines Added: 78, Lines Deleted: 0; 3647 bytes

@@ -6453,6 +6453,36 @@
 
           <listitem>
             <indexterm>
+              <primary>BackupReportFrequency</primary>
+            </indexterm>
+            
+            &mccge-warning-begin;
+            
+            <para id="mysql-cluster-param-ndbd-definition-backupreportfrequency">
+              This parameter controls how often backup status reports
+              are issued in the management client during a backup, as
+              well as how often such reports are written to the cluster
+              log (provided cluster event logging is configured to allow
+              it &mdash; see
+              <xref linkend="mysql-cluster-logging-and-checkpointing"/>).
+              <literal>BackupReportFrequency</literal> represents the
+              time in seconds between backup status reports.
+            </para>
+
+            <para>
+              The default value is 0.
+            </para>
+
+            <para>
+              This parameter was added in MySQL 5.1.18-ndb-6.2.2.
+            </para>
+            
+            &mccge-warning-end-cluster;
+            
+          </listitem>
+
+          <listitem>
+            <indexterm>
              
<primary><literal>BackupWriteSize</literal></primary>
             </indexterm>
 

@@ -7632,6 +7662,15 @@
                 <entry>N</entry>
               </row>
               <row>
+                <entry><literal><link
linkend="mysql-cluster-param-ndbd-definition-backupreportfrequency">BackupReportFrequency</link>
+                  (Added in MySQL 5.1.18-ndb-6.2.2)</literal></entry>
+                <entry>seconds</entry>
+                <entry>0</entry>
+                <entry>0</entry>
+                <entry>4294967039</entry>
+                <entry>N</entry>
+              </row>
+              <row>
                 <entry><literal><link
linkend="mysql-cluster-param-ndbd-definition-backupwritesize">BackupWriteSize</link></literal></entry>
                 <entry>bytes</entry>
                 <entry>32K</entry>

@@ -11556,6 +11595,45 @@
         <listitem>
           <indexterm>
             <primary>MySQL Cluster</primary>
+            <secondary><literal>REPORT</literal>
command</secondary>
+          </indexterm>
+
+          <indexterm>
+            <primary><literal>REPORT</literal> command (MySQL
Cluster)</primary>
+          </indexterm>
+          
+          &mccge-warning-begin;
+
+          <para>
+            <literal><replaceable>node_id</replaceable> REPORT
+            <replaceable>report-type</replaceable></literal>
+          </para>
+
+          <para>
+            Displays a report of type
+            <replaceable>report-type</replaceable> for the data node
+            identified by <replaceable>node_id</replaceable>, or for all
+            data nodes using <literal>ALL</literal>.
+          </para>
+
+          <para>
+            Currently, the only accepted value for
+            <replaceable>report-type</replaceable> is
+            <literal>BackupStatus</literal>, which provides a status
+            report on a cluster backup in progress.
+          </para>
+
+          <para>
+            The REPORT command was introduced in MySQL 5.1.8-ndb-6.2.2.
+          </para>
+          
+          &mccge-warning-end-cluster;
+          
+        </listitem>
+
+        <listitem>
+          <indexterm>
+            <primary>MySQL Cluster</primary>
             <secondary>single user mode</secondary>
           </indexterm>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-06-13 20:12:36 UTC (rev 6786)
+++ trunk/refman-5.1/news-5.1.xml	2007-06-13 21:22:20 UTC (rev 6787)
Changed blocks: 2, Lines Added: 35, Lines Deleted: 1; 1970 bytes

@@ -3324,7 +3324,7 @@
 
     <section id="news-5-1-18-ndb-6-2-2">
 
-      <title>Changes in release MySQL 5.1.18-ndb-6.2.2-beta (Not yet
released)</title>
+      <title>Changes in release MySQL 5.1.18-ndb-6.2.2-beta (07 May
2007)</title>
 
       <para role="release-level">
         This is a new Beta development release, fixing recently

@@ -3402,6 +3402,40 @@
           </para>
         </listitem>
 
+        <listitem>
+          <para>
+            Backup reporting functionality has been significantly
+            enhanced in this release:
+
+            <itemizedlist>
+
+              <listitem>
+                <para>
+                  A new configuration parameter
+                  <literal>BackupReportFrequency</literal> now makes it
+                  possible to cause the management client to provide
+                  status reports at regular intervals as well as for
+                  such reports to be written to the cluster log
+                  (depending on cluster event logging levels). See
+                  <xref linkend="mysql-cluster-ndbd-definition"/>, for
+                  more information about this parameter.
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  A new <literal>REPORT BackupStatus</literal> command
+                  has been added in the cluster management client which
+                  allows you to obtain a backup status report at any
+                  time during a backup. For more about this command, see
+                  <xref linkend="mysql-cluster-mgm-client-commands"/>.
+                </para>
+              </listitem>
+
+            </itemizedlist>
+          </para>
+        </listitem>
+
       </itemizedlist>
 
 <!--