svn commit - mysqldoc@oter02: r25244 - trunk/mysql-monitor-2.3

[john.russell]

Author: jdrussel
Date: 2011-03-04 00:00:43 +0100 (Fri, 04 Mar 2011)
New Revision: 25244

Log:
Apply the fix from JIRA issue #5185.


Modified:
   trunk/mysql-monitor-2.3/install-postinstall.xml
   trunk/mysql-monitor-2.3/mem-reference.xml


Modified: trunk/mysql-monitor-2.3/install-postinstall.xml
===================================================================
--- trunk/mysql-monitor-2.3/install-postinstall.xml	2011-03-03 20:52:11 UTC (rev 25243)
+++ trunk/mysql-monitor-2.3/install-postinstall.xml	2011-03-03 23:00:43 UTC (rev 25244)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 4; 734 bytes

@@ -59,10 +59,8 @@
 
     <listitem>
       <para>
-        <emphasis role="bold">Back up the repository</emphasis>: For a
-        back-up strategy suitable to your circumstances, see the
-        <ulink url="&base-url-docs;">MySQL reference manual
-        documentation</ulink>.
+        <emphasis role="bold">Back up the repository</emphasis>: For
+        details, see <xref linkend="mem-deployment-backup"/>.
       </para>
     </listitem>
 


Modified: trunk/mysql-monitor-2.3/mem-reference.xml
===================================================================
--- trunk/mysql-monitor-2.3/mem-reference.xml	2011-03-03 20:52:11 UTC (rev 25243)
+++ trunk/mysql-monitor-2.3/mem-reference.xml	2011-03-03 23:00:43 UTC (rev 25244)
Changed blocks: 5, Lines Added: 29, Lines Deleted: 16; 3926 bytes

@@ -531,19 +531,24 @@
     </indexterm>
 
     <para>
-      If you want to backup the data stored within your &merlin_server;,
-      you can use any of the typical backup solutions, such as the MySQL
+      To back up the data stored within your &merlin_server;, you can
+      use any of the typical backup solutions, such as the MySQL
       Enterprise Backup product or the <literal>mysqldump</literal>
-      command, to save your data. All you need to backup the information
-      is host name, user name and password details that were set during
-      the installation of the &merlin_server;.
+      command, to back up the
+      <link linkend="glos_repository">repository</link> database. Once
+      this database grows to substantial size, you might find that the
+      binary copy technique of the MySQL Enterprise Backup product is
+      faster (especially for restoring) than a logical backup using the
+      <literal>mysqldump</literal> command.
     </para>
 
     <para>
-      You can locate this information by examining the contents of the
+      To back up the &merlin; data, you need the host name, user name,
+      and password that were set during the installation of the
+      &merlin_server;. Locate this information in the
       <filename>configuration_report.txt</filename> file that was
-      generated when &merlin_server; was installed. A scample of the
-      file is provided below:
+      generated when &merlin_server; was installed. A sample of the file
+      is provided below:
     </para>
 
 <programlisting>MySQL Enterprise Monitor (Version 2.0.0.7088 : 20081031_152749_r7088)

@@ -574,8 +579,8 @@
     </para>
 
     <para>
-      To backup this information using <literal>mysqldump</literal> you
-      might use the following command:
+      To back up this information using <literal>mysqldump</literal>,
+      you might use the following command:
     </para>
 
 <programlisting>shell&gt; mysqldump --single-transaction &raquo;

@@ -589,7 +594,7 @@
 
     <para>
       To ensure consistency in a recovery situation, you may also want
-      to backup the agent configuration and metadata stored on each
+      to back up the agent configuration and metadata stored on each
       monitored MySQL server. To do this:
     </para>
 

@@ -597,19 +602,19 @@
 
       <listitem>
         <para>
-          Backup the configuration files of each agent. You should keep
-          a copy of the <filename>etc</filename> directory for each
-          agent. This directory contains the main configuration file,
+          Copy the <filename>etc</filename> subdirectory of each agent
+          to a backup location. This directory contains the main
+          configuration file,
           <filename>mysql-monitor-agent.ini</filename>, and the
           configuration information for each server being monitored,
           which is stored within the <filename>etc/instances</filename>
-          directory.
+          subdirectory.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          On each server being monitored, retain a copy of the
+          On each server being monitored, back up the
           <literal>mysql.inventory</literal> table, which contains the
           unique ID of the MySQL server.
         </para>

@@ -617,6 +622,14 @@
 
     </itemizedlist>
 
+    <para>
+      In case the backup process makes the Service Manager unresponsive
+      for a time, you might also adjust the
+      <literal role="sysvar">agent-backlog-timeout</literal> setting as
+      appropriate, to avoid losing data from the agents during a backup
+      of the repository database.
+    </para>
+
   </section>
 
   <section id="mem-deployment-migration-2-0">