svn commit - mysqldoc@docsrva: r10990 - in trunk: . refman-6.0

[paul]

Author: paul
Date: 2008-06-20 17:14:55 +0200 (Fri, 20 Jun 2008)
New Revision: 10990

Log:
 r32133@frost:  paul | 2008-06-20 10:15:35 -0500
 Backup terminology changes suggested by Rafal.


Modified:
   trunk/refman-6.0/backup.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:32131
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31778
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:32133
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31778


Modified: trunk/refman-6.0/backup.xml
===================================================================
--- trunk/refman-6.0/backup.xml	2008-06-20 14:55:05 UTC (rev 10989)
+++ trunk/refman-6.0/backup.xml	2008-06-20 15:14:55 UTC (rev 10990)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 11; 2242 bytes

@@ -1183,15 +1183,15 @@
     <para>
       The <literal>BACKUP DATABASE</literal> and
       <literal>RESTORE</literal> statements are available as of MySQL
-      6.0.5. They provide a way to make a copy of a MySQL server
-      instance (data and metadata) at a given point in time, and a way
-      to restore the instance to its state as of that time. Restoring a
-      backup can be combined with use of the binary log to accomplish
-      point-in-time recovery: If the restore operation is done because
-      data loss has occurred after the backup was made, restored
-      databases can be brought up to the time of data loss by executing
-      the data changes in the binary log between the times when the
-      backup was made and when the data loss occurred.
+      6.0.5. They provide a way to make a copy of a database or set of
+      databases at a given point in time, and a way to restore each
+      database to its state as of that time. Restoring a backup can be
+      combined with use of the binary log to accomplish point-in-time
+      recovery: If the restore operation is done because data loss has
+      occurred after the backup was made, restored databases can be
+      brought up to the time of data loss by executing the data changes
+      in the binary log between the times when the backup was made and
+      when the data loss occurred.
     </para>
 
     <para>

@@ -1348,8 +1348,8 @@
       <para>
         A backup operation begins at time <replaceable>t1</replaceable>
         and ends at time <replaceable>t2</replaceable>, producing a
-        backup image that contains the backup state (server instance
-        state) at time <replaceable>t</replaceable>, where
+        backup image that contains the backup state (database state) at
+        time <replaceable>t</replaceable>, where
         <replaceable>t1</replaceable> &lt;
<replaceable>t</replaceable>
         &lt; <replaceable>t2</replaceable>. The time
         <replaceable>t</replaceable> is called the validity point of the