svn commit - mysqldoc@docsrva: r23843 - trunk/dynamic-docs/glossary

[john.russell]

Author: jrussell
Date: 2010-11-19 00:02:13 +0100 (Fri, 19 Nov 2010)
New Revision: 23843

Log:
Some more terminology needed for the MEB webinar.


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


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2010-11-18 21:40:54 UTC (rev 23842)
+++ trunk/dynamic-docs/glossary/innodb.xml	2010-11-18 23:02:13 UTC (rev 23843)
Changed blocks: 2, Lines Added: 82, Lines Deleted: 0; 3203 bytes

@@ -3131,6 +3131,27 @@
 
   </glossent>
 
+  <glossent id="logical_backup">
+
+    <gterm>logical backup</gterm>
+    <def>
+
+      <para>
+        A <emphasis role="bold">backup</emphasis> that reproduces table
+        structure and data, without copying the actual data files. For
+        example, the <literal>mysqldump</literal> command produces a
+        logical backup, because its output contains statements such as
+        <literal>CREATE TABLE</literal> and <literal>INSERT</literal>
+        that can re-create the data. Contrast with
+        <emphasis role="bold">physical backup</emphasis>.
+      </para>
+
+    </def>
+    <gseealso glosid="backup" />
+    <gseealso glosid="physical_backup" />
+
+  </glossent>
+
   <glossent id="loose_">
 
     <gterm>loose_</gterm>

@@ -4136,6 +4157,67 @@
 
   </glossent>
 
+  <glossent id="physical_backup">
+
+    <gterm>physical backup</gterm>
+    <def>
+
+      <para>
+        A <emphasis role="bold">backup</emphasis> that copies the actual
+        data files. For example, the <emphasis role="bold">MySQL
+        Enterprise Backup</emphasis> command produces a physical backup,
+        because its output contains data files that can be used directly
+        by the <literal>mysqld</literal> server. Contrast with
+        <emphasis role="bold">logical backup</emphasis>.
+      </para>
+
+    </def>
+    <gseealso glosid="backup" />
+    <gseealso glosid="mysql_enterprise_backup" />
+    <gseealso glosid="logical_backup" />
+
+  </glossent>
+
+  <glossent id="pitr">
+
+    <gterm>PITR backup</gterm>
+    <def>
+        Acronym for <emphasis role="bold">point-in-time recovery</emphasis>.
+    </def>
+    <gseealso glosid="point_in_time_recovery" />
+
+  </glossent>
+
+  <glossent id="point_in_time_recovery">
+
+    <gterm>point-in-time recovery</gterm>
+    <def>
+
+      <para>
+        The process of restoring a
+        <emphasis role="bold">backup</emphasis> to recreate the state of
+        the database at a specific date and time. Commonly abbreviated
+        <emphasis role="bold">PITR</emphasis>. Because it is unlikely
+        that the specified time corresponds exactly to the time of a
+        backup, this technique usually requires a combination of a
+        <emphasis role="bold">physical backup</emphasis> and a
+        <emphasis role="bold">logical backup</emphasis>. For example,
+        with the <emphasis role="bold">MySQL Enterprise
+        Backup</emphasis> product, you restore the last backup that you
+        took before the specified point in time, then replay changes
+        from the <emphasis role="bold">binary log</emphasis> between the
+        time of the backup and the PITR time.
+      </para>
+
+    </def>
+    <gseealso glosid="backup" />
+    <gseealso glosid="mysql_enterprise_backup" />
+    <gseealso glosid="logical_backup" />
+    <gseealso glosid="physical_backup" />
+    <gseealso glosid="pitr" />
+
+  </glossent>
+
   <glossent id="prepared_backup">
 
     <gterm>prepared backup</gterm>