List:Commits« Previous MessageNext Message »
From:john.russell Date:May 17 2011 11:40pm
Subject:svn commit - mysqldoc@oter02: r26257 - trunk/dynamic-docs/glossary
View as plain text  
Author: jdrussel
Date: 2011-05-18 01:40:38 +0200 (Wed, 18 May 2011)
New Revision: 26257

Log:
Filling in some bits that are useful to reference from the Ref Man.


Modified:
   trunk/dynamic-docs/glossary/backup.xml


Modified: trunk/dynamic-docs/glossary/backup.xml
===================================================================
--- trunk/dynamic-docs/glossary/backup.xml	2011-05-17 19:40:09 UTC (rev 26256)
+++ trunk/dynamic-docs/glossary/backup.xml	2011-05-17 23:40:38 UTC (rev 26257)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 3; 1394 bytes

@@ -359,13 +359,15 @@
         A <emphasis role="bold">backup</emphasis> that includes all the
         <emphasis role="bold">tables</emphasis> in each MySQL database,
         and all the databases in a MySQL instance. Contrast with
-        <emphasis role="bold">partial backup</emphasis>.
+        <emphasis role="bold">partial backup</emphasis> and
+        <emphasis role="bold">incremental backup</emphasis>.
       </para>
 
     </def>
     <gseealso glosid="backup"/>
     <gseealso glosid="table"/>
     <gseealso glosid="partial_backup"/>
+    <gseealso glosid="incremental_backup"/>
 
   </glossent>
 

@@ -492,10 +494,16 @@
     <gterm>incremental backup</gterm>
     <def>
 
-      <para></para>
+      <para>
+        A backup that captures only data changed since the previous
+        backup. It has the potential to be smaller and faster than a
+        <emphasis role="bold">full backup</emphasis>. The incremental
+        backup data must be merged with the contents of the previous
+        backup before it can be restored.
+      </para>
 
     </def>
-    <gseealso glosid=""/>
+    <gseealso glosid="full_backup"/>
 
   </glossent>
 


Thread
svn commit - mysqldoc@oter02: r26257 - trunk/dynamic-docs/glossaryjohn.russell19 May