Author: jstephens
Date: 2006-06-20 09:20:34 +0200 (Tue, 20 Jun 2006)
New Revision: 2427
Log:
Cluster Backups Using Management Server -> Management Client (thanks, Kolbe!)
Modified:
trunk/refman-4.1/ndbcluster.xml
trunk/refman-4.1/renamed-nodes.txt
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.0/renamed-nodes.txt
trunk/refman-5.1/ndbcluster.xml
trunk/refman-5.1/renamed-nodes.txt
trunk/refman-common/titles.en.ent
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-4.1/ndbcluster.xml 2006-06-20 07:20:34 UTC (rev 2427)
@@ -2030,7 +2030,7 @@
<para>
For information on making Cluster backups, see
- <xref linkend="mysql-cluster-backup-using-management-server"/>.
+ <xref linkend="mysql-cluster-backup-using-management-client"/>.
</para>
<para>
@@ -11336,9 +11336,9 @@
</section>
- <section id="mysql-cluster-backup-using-management-server">
+ <section id="mysql-cluster-backup-using-management-client">
- <title>&title-mysql-cluster-backup-using-management-server;</title>
+ <title>&title-mysql-cluster-backup-using-management-client;</title>
<indexterm>
<primary>MySQL Cluster</primary>
@@ -11357,7 +11357,7 @@
</para>
<para>
- Creating a backup using the management server involves the
+ Creating a backup using the management client involves the
following steps:
</para>
@@ -11365,7 +11365,7 @@
<listitem>
<para>
- Start the management server (<command>ndb_mgm</command>).
+ Start the management client (<command>ndb_mgm</command>).
</para>
</listitem>
@@ -11386,16 +11386,16 @@
<listitem>
<para>
- The management server will reply with the message
+ The management client will reply with the message
<literal>Start of backup ordered</literal>. This means
- that the management server has submitted the request to
+ that the management client has submitted the request to
the cluster, but has not yet received any response.
</para>
</listitem>
<listitem>
<para>
- The management server will reply <literal>Backup
+ The management client will reply <literal>Backup
<replaceable>backup_id</replaceable> started</literal>,
where <replaceable>backup_id</replaceable> is the unique
identifier for this particular backup. (This identifier
@@ -11409,7 +11409,7 @@
<listitem>
<para>
- The management server will signal that the backup is
+ The management client will signal that the backup is
finished with the message <literal>Backup
<replaceable>backup_id</replaceable> completed</literal>.
</para>
@@ -11425,7 +11425,7 @@
<listitem>
<para>
- Start the management server.
+ Start the management client.
</para>
</listitem>
@@ -11435,7 +11435,7 @@
<replaceable>backup_id</replaceable></literal>. The number
<replaceable>backup_id</replaceable> is the identifier of
the backup that was included in the response of the
- management server when the backup was started (in the
+ management client when the backup was started (in the
message <literal>Backup
<replaceable>backup_id</replaceable> started</literal>).
</para>
@@ -11443,7 +11443,7 @@
<listitem>
<para>
- The management server will acknowledge the abort request
+ The management client will acknowledge the abort request
with <literal>Abort of backup
<replaceable>backup_id</replaceable> ordered</literal>;
note that it has received no actual response to this
@@ -11453,7 +11453,7 @@
<listitem>
<para>
- After the backup has been aborted, the management server
+ After the backup has been aborted, the management client
will report <literal>Backup
<replaceable>backup_id</replaceable> has been aborted for
reason <replaceable>XYZ</replaceable></literal>. This
@@ -11477,7 +11477,7 @@
<para>
<emphasis role="bold">Note</emphasis>: If there is no backup
with ID <replaceable>backup_id</replaceable> running when it
- is aborted, the management server makes no explicit response.
+ is aborted, the management client makes no explicit response.
However, the fact that an invalid abort command was sent is
indicated in the cluster log.
</para>
Modified: trunk/refman-4.1/renamed-nodes.txt
===================================================================
--- trunk/refman-4.1/renamed-nodes.txt 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-4.1/renamed-nodes.txt 2006-06-20 07:20:34 UTC (rev 2427)
@@ -52,6 +52,7 @@
myisam myisam-storage-engine
mysql-apis apis
mysql-cluster-limitations-in-4-1 mysql-cluster-limitations
+mysql-cluster-backup-using-management-server mysql-cluster-backup-using-management-client
mysql-connectors connectors
mysql-database-administration database-administration
mysql-optimisation optimization
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-5.0/ndbcluster.xml 2006-06-20 07:20:34 UTC (rev 2427)
@@ -2032,7 +2032,7 @@
<para>
For information on making Cluster backups, see
- <xref linkend="mysql-cluster-backup-using-management-server"/>.
+ <xref linkend="mysql-cluster-backup-using-management-client"/>.
</para>
<para>
@@ -11388,9 +11388,9 @@
</section>
- <section id="mysql-cluster-backup-using-management-server">
+ <section id="mysql-cluster-backup-using-management-client">
- <title>&title-mysql-cluster-backup-using-management-server;</title>
+ <title>&title-mysql-cluster-backup-using-management-client;</title>
<indexterm>
<primary>MySQL Cluster</primary>
@@ -11409,7 +11409,7 @@
</para>
<para>
- Creating a backup using the management server involves the
+ Creating a backup using the management client involves the
following steps:
</para>
@@ -11417,7 +11417,7 @@
<listitem>
<para>
- Start the management server (<command>ndb_mgm</command>).
+ Start the management client (<command>ndb_mgm</command>).
</para>
</listitem>
@@ -11438,16 +11438,16 @@
<listitem>
<para>
- The management server will reply with the message
+ The management client will reply with the message
<literal>Start of backup ordered</literal>. This means
- that the management server has submitted the request to
+ that the management client has submitted the request to
the cluster, but has not yet received any response.
</para>
</listitem>
<listitem>
<para>
- The management server will reply <literal>Backup
+ The management client will reply <literal>Backup
<replaceable>backup_id</replaceable> started</literal>,
where <replaceable>backup_id</replaceable> is the unique
identifier for this particular backup. (This identifier
@@ -11461,7 +11461,7 @@
<listitem>
<para>
- The management server will signal that the backup is
+ The management client will signal that the backup is
finished with the message <literal>Backup
<replaceable>backup_id</replaceable> completed</literal>.
</para>
@@ -11477,7 +11477,7 @@
<listitem>
<para>
- Start the management server.
+ Start the management client.
</para>
</listitem>
@@ -11487,7 +11487,7 @@
<replaceable>backup_id</replaceable></literal>. The number
<replaceable>backup_id</replaceable> is the identifier of
the backup that was included in the response of the
- management server when the backup was started (in the
+ management client when the backup was started (in the
message <literal>Backup
<replaceable>backup_id</replaceable> started</literal>).
</para>
@@ -11495,7 +11495,7 @@
<listitem>
<para>
- The management server will acknowledge the abort request
+ The management client will acknowledge the abort request
with <literal>Abort of backup
<replaceable>backup_id</replaceable> ordered</literal>;
note that it has received no actual response to this
@@ -11505,7 +11505,7 @@
<listitem>
<para>
- After the backup has been aborted, the management server
+ After the backup has been aborted, the management client
will report <literal>Backup
<replaceable>backup_id</replaceable> has been aborted for
reason <replaceable>XYZ</replaceable></literal>. This
@@ -11529,7 +11529,7 @@
<para>
<emphasis role="bold">Note</emphasis>: If there is no backup
with ID <replaceable>backup_id</replaceable> running when it
- is aborted, the management server makes no explicit response.
+ is aborted, the management client makes no explicit response.
However, the fact that an invalid abort command was sent is
indicated in the cluster log.
</para>
Modified: trunk/refman-5.0/renamed-nodes.txt
===================================================================
--- trunk/refman-5.0/renamed-nodes.txt 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-5.0/renamed-nodes.txt 2006-06-20 07:20:34 UTC (rev 2427)
@@ -51,6 +51,7 @@
merge merge-storage-engine
myisam myisam-storage-engine
mysql-apis apis
+mysql-cluster-backup-using-management-server mysql-cluster-backup-using-management-client
mysql-connectors connectors
mysql-database-administration database-administration
mysql-optimisation optimization
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-5.1/ndbcluster.xml 2006-06-20 07:20:34 UTC (rev 2427)
@@ -2023,7 +2023,7 @@
<para>
For information on making Cluster backups, see
- <xref linkend="mysql-cluster-backup-using-management-server"/>.
+ <xref linkend="mysql-cluster-backup-using-management-client"/>.
</para>
<para>
@@ -11378,9 +11378,9 @@
</section>
- <section id="mysql-cluster-backup-using-management-server">
+ <section id="mysql-cluster-backup-using-management-client">
- <title>&title-mysql-cluster-backup-using-management-server;</title>
+ <title>&title-mysql-cluster-backup-using-management-client;</title>
<indexterm>
<primary>MySQL Cluster</primary>
@@ -11399,7 +11399,7 @@
</para>
<para>
- Creating a backup using the management server involves the
+ Creating a backup using the management client involves the
following steps:
</para>
@@ -11407,7 +11407,7 @@
<listitem>
<para>
- Start the management server (<command>ndb_mgm</command>).
+ Start the management client (<command>ndb_mgm</command>).
</para>
</listitem>
@@ -11428,16 +11428,16 @@
<listitem>
<para>
- The management server will reply with the message
+ The management client will reply with the message
<literal>Start of backup ordered</literal>. This means
- that the management server has submitted the request to
+ that the management client has submitted the request to
the cluster, but has not yet received any response.
</para>
</listitem>
<listitem>
<para>
- The management server will reply <literal>Backup
+ The management client will reply <literal>Backup
<replaceable>backup_id</replaceable> started</literal>,
where <replaceable>backup_id</replaceable> is the unique
identifier for this particular backup. (This identifier
@@ -11451,7 +11451,7 @@
<listitem>
<para>
- The management server will signal that the backup is
+ The management client will signal that the backup is
finished with the message <literal>Backup
<replaceable>backup_id</replaceable> completed</literal>.
</para>
@@ -11467,7 +11467,7 @@
<listitem>
<para>
- Start the management server.
+ Start the management client.
</para>
</listitem>
@@ -11477,7 +11477,7 @@
<replaceable>backup_id</replaceable></literal>. The number
<replaceable>backup_id</replaceable> is the identifier of
the backup that was included in the response of the
- management server when the backup was started (in the
+ management client when the backup was started (in the
message <literal>Backup
<replaceable>backup_id</replaceable> started</literal>).
</para>
@@ -11485,7 +11485,7 @@
<listitem>
<para>
- The management server will acknowledge the abort request
+ The management client will acknowledge the abort request
with <literal>Abort of backup
<replaceable>backup_id</replaceable> ordered</literal>;
note that it has received no actual response to this
@@ -11495,7 +11495,7 @@
<listitem>
<para>
- After the backup has been aborted, the management server
+ After the backup has been aborted, the management client
will report <literal>Backup
<replaceable>backup_id</replaceable> has been aborted for
reason <replaceable>XYZ</replaceable></literal>. This
@@ -11519,7 +11519,7 @@
<para>
<emphasis role="bold">Note</emphasis>: If there is no backup
with ID <replaceable>backup_id</replaceable> running when it
- is aborted, the management server makes no explicit response.
+ is aborted, the management client makes no explicit response.
However, the fact that an invalid abort command was sent is
indicated in the cluster log.
</para>
Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-5.1/renamed-nodes.txt 2006-06-20 07:20:34 UTC (rev 2427)
@@ -54,10 +54,11 @@
merge merge-storage-engine
myisam myisam-storage-engine
mysql-apis apis
+mysql-cluster-5-0-changes mysql-cluster-5-1-changes
+mysql-cluster-5-1-roadmap mysql-cluster-5-1-changes
+mysql-cluster-backup-using-management-server mysql-cluster-backup-using-management-client
mysql-connectors connectors
mysql-database-administration database-administration
-mysql-cluster-5-0-changes mysql-cluster-5-1-changes
-mysql-cluster-5-1-roadmap mysql-cluster-5-1-changes
mysql-optimisation optimization
nt-start windows-start-service
nutshell-ready-for-immediate-use roadmap
Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent 2006-06-20 07:17:25 UTC (rev 2426)
+++ trunk/refman-common/titles.en.ent 2006-06-20 07:20:34 UTC (rev 2427)
@@ -1020,7 +1020,7 @@
<!ENTITY title-mysql-cluster-backup-concepts "Cluster Backup Concepts">
<!ENTITY title-mysql-cluster-backup-configuration "Configuration for Cluster Backup">
<!ENTITY title-mysql-cluster-backup-troubleshooting "Backup Troubleshooting">
-<!ENTITY title-mysql-cluster-backup-using-management-server "Using The Management Server to Create a Backup">
+<!ENTITY title-mysql-cluster-backup-using-management-client "Using The Management Client to Create a Backup">
<!ENTITY title-mysql-cluster-basics "Basic MySQL Cluster Concepts">
<!ENTITY title-mysql-cluster-building "Building MySQL Cluster from Source Code">
<!ENTITY title-mysql-cluster-change-history "Changes in MySQL Cluster">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2427 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | jon | 20 Jun |
