List:Commits« Previous MessageNext Message »
From:john.russell Date:July 14 2010 11:38pm
Subject:svn commit - mysqldoc@docsrva: r21736 - trunk/mysql-enterprise-backup-3.5
View as plain text  
Author: jrussell
Date: 2010-07-15 01:38:59 +0200 (Thu, 15 Jul 2010)
New Revision: 21736

Log:
Reformat, as recent changes probably resulted in
inconsistent line lengths.


Modified:
   trunk/mysql-enterprise-backup-3.5/manual.xml


Modified: trunk/mysql-enterprise-backup-3.5/manual.xml
===================================================================
--- trunk/mysql-enterprise-backup-3.5/manual.xml	2010-07-14 23:37:54 UTC (rev 21735)
+++ trunk/mysql-enterprise-backup-3.5/manual.xml	2010-07-14 23:38:59 UTC (rev 21736)
Changed blocks: 6, Lines Added: 42, Lines Deleted: 36; 6876 bytes

@@ -108,12 +108,15 @@
       the <link linkend="glos_ibdata_file">ibdata* files</link> that
       represent the <link linkend="glos_system_tablespace">system
       tablespace</link> and possibly the data for some user tables; any
-      <link linkend="glos_ibd_file">.ibd files</link>, containing data from user tables
-      created with the <link linkend="glos_file_per_table">file-per-table</link> setting
-      enabled; data extracted from the <link linkend="glos_ib_logfile">ib_logfile*
-      files</link> (the <link linkend="glos_redo_log">redo
-      log</link> information representing changes that occur while the backup is running), which is stored
-      in a new backup file <link linkend="glos_ibbackup_logfile">ibbackup_logfile</link>.
+      <link linkend="glos_ibd_file">.ibd files</link>, containing data
+      from user tables created with the
+      <link linkend="glos_file_per_table">file-per-table</link> setting
+      enabled; data extracted from the
+      <link linkend="glos_ib_logfile">ib_logfile* files</link> (the
+      <link linkend="glos_redo_log">redo log</link> information
+      representing changes that occur while the backup is running),
+      which is stored in a new backup file
+      <link linkend="glos_ibbackup_logfile">ibbackup_logfile</link>.
     </para>
 
     <para>

@@ -124,16 +127,16 @@
 
     <para>
       The files, as they are originally copied, form a
-      <link linkend="glos_raw_backup">raw backup</link> that requires further processing
-      to be ready to be restored. You must then
-      run the <link linkend="glos_apply">apply</link> step, which
-      updates the backup files based on the changes recorded in the
+      <link linkend="glos_raw_backup">raw backup</link> that requires
+      further processing to be ready to be restored. You must then run
+      the <link linkend="glos_apply">apply</link> step, which updates
+      the backup files based on the changes recorded in the
       <literal>ibbackup_logfile</literal> file, producing a
       <link linkend="glos_prepared_backup">prepared backup</link>. At
       this point, the backup data corresponds to a single point in time.
-      The files are now ready to be restored to their original
-      location, or for testing or other use of the backup
-      data by running <literal>mysqld</literal> in a new data directory.
+      The files are now ready to be restored to their original location,
+      or for testing or other use of the backup data by running
+      <literal>mysqld</literal> in a new data directory.
     </para>
 
     <para>

@@ -335,11 +338,10 @@
 
       <para>
         Because <literal>ibbackup</literal> <emphasis role="bold">does
-        not write over any files</emphasis> during the initial backup step,
-        the backup directory must not
-        contain any old backup files. <literal>ibbackup</literal> stops
-        when asked to create a file that already exists, to avoid
-        harming an existing backup.
+        not write over any files</emphasis> during the initial backup
+        step, the backup directory must not contain any old backup
+        files. <literal>ibbackup</literal> stops when asked to create a
+        file that already exists, to avoid harming an existing backup.
       </para>
 
     </section>

@@ -991,42 +993,45 @@
         You can use the <literal>ibbackup</literal> option
         <literal>--suspend-at-end</literal> to make a point-in-time
         backup of both MyISAM and InnoDB tables. This option pauses the
-	backup process
-        when an <literal>ibbackup</literal>
-        run is close to ending, so that a script written by you can copy the MyISAM tables
-        to a backup. Since the backup taken by
+        backup process when an <literal>ibbackup</literal> run is close
+        to ending, so that a script written by you can copy the MyISAM
+        tables to a backup. Since the backup taken by
         <literal>ibbackup</literal> corresponds to the time at the end
-        of the run, and your script will block modifications to the MyISAM tables
-        at that point, the backup contains a snapshot of MyISAM tables
-        at the same point in time. Your script must follow this outline:
+        of the run, and your script will block modifications to the
+        MyISAM tables at that point, the backup contains a snapshot of
+        MyISAM tables at the same point in time. Your script must follow
+        this outline:
       </para>
 
       <itemizedlist>
 
         <listitem>
           <para>
-            Issue the command <literal>ibbackup --suspend-at-end</literal> ...;
+            Issue the command <literal>ibbackup
+            --suspend-at-end</literal> ...;
           </para>
         </listitem>
 
         <listitem>
           <para>
             Periodically check for the existence of the file
-            <literal>ibbackup_suspended</literal>. When this file appears, your script must:
+            <literal>ibbackup_suspended</literal>. When this file
+            appears, your script must:
           </para>
 
           <orderedlist>
 
             <listitem>
               <para>
-                Issue the statement <literal>FLUSH TABLES WITH READ LOCK;</literal>
+                Issue the statement <literal>FLUSH TABLES WITH READ
+                LOCK;</literal>
               </para>
             </listitem>
 
             <listitem>
               <para>
-                Manually copy all <literal>.frm</literal> files,
-                MyISAM tables, and other non-InnoDB files from database
+                Manually copy all <literal>.frm</literal> files, MyISAM
+                tables, and other non-InnoDB files from database
                 directories to a backup location.
               </para>
             </listitem>

@@ -1040,7 +1045,8 @@
 
             <listitem>
               <para>
-                Wait until the <literal>ibbackup</literal> command finishes.
+                Wait until the <literal>ibbackup</literal> command
+                finishes.
               </para>
             </listitem>
 

@@ -4428,11 +4434,11 @@
         library that is used for the compressed backup feature:
       </para>
 
-<para>
-Oracle gratefully acknowledges the contributions of Jean-loup
-Gailly and Mark Adler in creating the zlib general purpose
-compression library which is used in this product.
-</para>
+      <para>
+        Oracle gratefully acknowledges the contributions of Jean-loup
+        Gailly and Mark Adler in creating the zlib general purpose
+        compression library which is used in this product.
+      </para>
 
 <programlisting>
 /* zlib.h -- interface of the 'zlib' general purpose compression


Thread
svn commit - mysqldoc@docsrva: r21736 - trunk/mysql-enterprise-backup-3.5john.russell15 Jul