List:Commits« Previous MessageNext Message »
From:paul.dubois Date:April 21 2010 7:50pm
Subject:svn commit - mysqldoc@docsrva: r20184 - in trunk: . mysql-backup
View as plain text  
Author: paul
Date: 2010-04-21 21:50:59 +0200 (Wed, 21 Apr 2010)
New Revision: 20184

Log:
 r58132@frost:  paul | 2010-04-21 14:50:32 -0500
 Add subsection markup


Modified:
   trunk/mysql-backup/backup.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:38445
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:58131
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:38445
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:58132
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/mysql-backup/backup.xml
===================================================================
--- trunk/mysql-backup/backup.xml	2010-04-21 19:50:49 UTC (rev 20183)
+++ trunk/mysql-backup/backup.xml	2010-04-21 19:50:59 UTC (rev 20184)
Changed blocks: 6, Lines Added: 97, Lines Deleted: 89; 9359 bytes

@@ -225,12 +225,16 @@
       restoration with point-in-time recovery.
     </para>
 
-    <para>
-      To make a backup, use the <literal role="stmt">BACKUP
-      DATABASE</literal> statement, which backs up one or more databases
-      to a named file on the server host:
-    </para>
+    <section id="mysql-backup-using-images">
 
+      <title>Creating and Restoring Backup Images</title>
+
+      <para>
+        To make a backup, use the <literal role="stmt">BACKUP
+        DATABASE</literal> statement, which backs up one or more
+        databases to a named file on the server host:
+      </para>
+
 <programlisting>
 mysql&gt; <userinput>BACKUP DATABASE world TO '/tmp/mybackupfile';</userinput>
 +-----------+

@@ -240,9 +244,9 @@
 +-----------+
 </programlisting>
 
-    <para>
-      To back up more than one database, separate the names by commas:
-    </para>
+      <para>
+        To back up more than one database, separate the names by commas:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>BACKUP DATABASE world, sakila TO '/tmp/mybackupfile';</userinput>

@@ -253,10 +257,10 @@
 +-----------+
 </programlisting>
 
-    <para>
-      To select all databases for backup, use the <literal>*</literal>
-      selector as a shortcut:
-    </para>
+      <para>
+        To select all databases for backup, use the <literal>*</literal>
+        selector as a shortcut:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>BACKUP DATABASE * TO '/tmp/mybackupfile';</userinput>

@@ -267,17 +271,17 @@
 +-----------+
 </programlisting>
 
-    <para>
-      Backup images should be stored in a secure location so that
-      unauthorized users cannot modify them, for example, by modifying
-      the <literal role="stmt">GRANT</literal> statements contained
-      therein to change the privileges granted by restore operations.
-    </para>
+      <para>
+        Backup images should be stored in a secure location so that
+        unauthorized users cannot modify them, for example, by modifying
+        the <literal role="stmt">GRANT</literal> statements contained
+        therein to change the privileges granted by restore operations.
+      </para>
 
-    <para>
-      To restore databases from the contents of a backup file, use the
-      <literal role="stmt">RESTORE</literal> statement:
-    </para>
+      <para>
+        To restore databases from the contents of a backup file, use the
+        <literal role="stmt">RESTORE</literal> statement:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>RESTORE FROM '/tmp/mybackupfile';</userinput>

@@ -288,11 +292,11 @@
 +-----------+
 </programlisting>
 
-    <para>
-      If the backup file restores databases that already exist, an error
-      occurs. To overwrite them, add the <literal>OVERWRITE</literal>
-      option:
-    </para>
+      <para>
+        If the backup file restores databases that already exist, an
+        error occurs. To overwrite them, add the
+        <literal>OVERWRITE</literal> option:
+      </para>
 
 <programlisting>
 mysql&gt; <userinput>RESTORE FROM '/tmp/mybackupfile' OVERWRITE;</userinput>

@@ -303,96 +307,100 @@
 +-----------+
 </programlisting>
 
-    <para>
-      All storage engines that are represented by tables in the backup
-      image must be enabled in the server on which a restore operation
-      is performed. For example, if a backup image contains
-      <literal role="se">ARCHIVE</literal> tables and the server does
-      not have the <literal role="se">ARCHIVE</literal> storage engine
-      enabled, the table cannot be restored and the operation fails.
-    </para>
+      <para>
+        All storage engines that are represented by tables in the backup
+        image must be enabled in the server on which a restore operation
+        is performed. For example, if a backup image contains
+        <literal role="se">ARCHIVE</literal> tables and the server does
+        not have the <literal role="se">ARCHIVE</literal> storage engine
+        enabled, the table cannot be restored and the operation fails.
+      </para>
 
-    <para>
-      As previously mentioned, <literal role="stmt">BACKUP
-      DATABASE</literal> does not back up the <literal>mysql</literal>
-      database. This database contains the grant tables that define user
-      accounts and their privileges, as well as other system
-      information. To make a full server instance backup that includes
-      account information in addition to data, use the
-      <literal role="stmt">BACKUP DATABASE</literal> statement together
-      with the <command>mysqldump</command> program. In the following
-      instructions, <replaceable>path</replaceable> represents the full
-      path name to the directory where you store your backup files.
-    </para>
+      <para>
+        As previously mentioned, <literal role="stmt">BACKUP
+        DATABASE</literal> does not back up the <literal>mysql</literal>
+        database. This database contains the grant tables that define
+        user accounts and their privileges, as well as other system
+        information. To make a full server instance backup that includes
+        account information in addition to data, use the
+        <literal role="stmt">BACKUP DATABASE</literal> statement
+        together with the <command>mysqldump</command> program. In the
+        following instructions, <replaceable>path</replaceable>
+        represents the full path name to the directory where you store
+        your backup files.
+      </para>
 
-    <orderedlist>
+      <orderedlist>
 
-      <listitem>
-        <para>
-          Use <command>mysqldump</command> to back up the
-          <literal>mysql</literal> database. This is a blocking
-          operation that prevents changes to the database during the
-          dump, but the <literal>mysql</literal> database normally is
-          relatively small and can be dumped quickly:
-        </para>
+        <listitem>
+          <para>
+            Use <command>mysqldump</command> to back up the
+            <literal>mysql</literal> database. This is a blocking
+            operation that prevents changes to the database during the
+            dump, but the <literal>mysql</literal> database normally is
+            relatively small and can be dumped quickly:
+          </para>
 
 <programlisting>
 shell&gt; <userinput>mysqldump --databases mysql &gt; <replaceable>path</replaceable>/mysql-db.sql</userinput>
 </programlisting>
-      </listitem>
+        </listitem>
 
-      <listitem>
-        <para>
-          Use <literal role="stmt">BACKUP DATABASE</literal> to back up
-          the data from other databases. This is a nonblocking
-          operation:
-        </para>
+        <listitem>
+          <para>
+            Use <literal role="stmt">BACKUP DATABASE</literal> to back
+            up the data from other databases. This is a nonblocking
+            operation:
+          </para>
 
 <programlisting>
 mysql&gt; <userinput>BACKUP DATABASE * TO '<replaceable>path</replaceable>/other-dbs.bak';</userinput>
 </programlisting>
-      </listitem>
+        </listitem>
 
-    </orderedlist>
+      </orderedlist>
 
-    <para>
-      Restore the server instance later like this:
-    </para>
+      <para>
+        Restore the server instance later like this:
+      </para>
 
-    <orderedlist>
+      <orderedlist>
 
-      <listitem>
-        <para>
-          To restore the user accounts, use the <command>mysql</command>
-          client to reload the <literal>mysql</literal> database dump
-          file produced by <command>mysqldump</command>:
-        </para>
+        <listitem>
+          <para>
+            To restore the user accounts, use the
+            <command>mysql</command> client to reload the
+            <literal>mysql</literal> database dump file produced by
+            <command>mysqldump</command>:
+          </para>
 
 <programlisting>
 shell&gt; <userinput>mysql -u root -p &lt; <replaceable>path</replaceable>/mysql-db.sql</userinput>
 </programlisting>
-      </listitem>
+        </listitem>
 
-      <listitem>
-        <para>
-          To restore the data for other databases, use
-          <literal role="stmt">RESTORE</literal> with the image file
-          produced by <literal role="stmt">BACKUP DATABASE</literal>:
-        </para>
+        <listitem>
+          <para>
+            To restore the data for other databases, use
+            <literal role="stmt">RESTORE</literal> with the image file
+            produced by <literal role="stmt">BACKUP DATABASE</literal>:
+          </para>
 
 <programlisting>
 mysql&gt; <userinput>RESTORE FROM '<replaceable>path</replaceable>/other-dbs.bak';</userinput>
 </programlisting>
-      </listitem>
+        </listitem>
 
-    </orderedlist>
+      </orderedlist>
 
-    <para>
-      For more information about <literal role="stmt">BACKUP
-      DATABASE</literal> and <literal role="stmt">RESTORE</literal>, see
-      <xref linkend="mysql-backup-sql"/>.
-    </para>
+      <para>
+        For more information about <literal role="stmt">BACKUP
+        DATABASE</literal> and <literal role="stmt">RESTORE</literal>,
+        see <xref linkend="mysql-backup-sql"/>.
+      </para>
 
+    </section>
+
     <section id="mysql-backup-image-contents">
 
       <title>Backup Image Contents</title>


Thread
svn commit - mysqldoc@docsrva: r20184 - in trunk: . mysql-backuppaul.dubois22 Apr