Author: paul
Date: 2008-09-23 09:12:53 +0200 (Tue, 23 Sep 2008)
New Revision: 11867
Log:
r34088@frost: paul | 2008-09-22 09:35:28 +0300
BACKUP DATABASE produces a consistent backup regardless of storage engine.
Non-MyISAM non-trx tables are locked for duration of backup operation.
Modified:
trunk/refman-6.0/backup.xml
trunk/refman-6.0/restrictions.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:34079
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33247
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34088
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33247
Modified: trunk/refman-6.0/backup.xml
===================================================================
--- trunk/refman-6.0/backup.xml 2008-09-23 06:06:56 UTC (rev 11866)
+++ trunk/refman-6.0/backup.xml 2008-09-23 07:12:53 UTC (rev 11867)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 6; 2019 bytes
@@ -1186,15 +1186,28 @@
<literal>RESTORE</literal> statements. 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>
+ A backup operation can include tables for different storage
+ engines and the backup image will still be consistent. That is,
+ you need not care which storage engines you're using.
+ <literal>BACKUP DATABASE</literal> saves the data in a consistent
+ backup image with respect to its <quote>validity point.</quote>
+ </para>
+
+ <para>
+ The validity point ties the backup to the binary log. 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 (that is, after
+ the validity point), 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>
A goal of the <literal>BACKUP DATABASE</literal> and
<literal>RESTORE</literal> statements is to enable other database
operations to proceed concurrently, to make it unnecessary to take
Modified: trunk/refman-6.0/restrictions.xml
===================================================================
--- trunk/refman-6.0/restrictions.xml 2008-09-23 06:06:56 UTC (rev 11866)
+++ trunk/refman-6.0/restrictions.xml 2008-09-23 07:12:53 UTC (rev 11867)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 830 bytes
@@ -1392,6 +1392,17 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The backup image is consistent and has a well-defined validity
+ point regardless of the storage engines used. However,
+ non-transactional tables are locked for the duration of the
+ <literal>BACKUP DATABASE</literal> operation if they use a
+ storage engine other than <literal>MyISAM</literal> (such as
+ <literal>ARCHIVE</literal> or <literal>MEMORY</literal>).
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11867 - in trunk: . refman-6.0 | paul.dubois | 23 Sep |
