You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by st...@apache.org on 2012/09/18 16:31:33 UTC

svn commit: r1387185 - /subversion/site/publish/docs/release-notes/1.8.html

Author: stsp
Date: Tue Sep 18 14:31:33 2012
New Revision: 1387185

URL: http://svn.apache.org/viewvc?rev=1387185&view=rev
Log:
* publish/docs/release-notes/1.8.html: Move incremental hotcopy description
   into the common admin tools section.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1387185&r1=1387184&r2=1387185&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Sep 18 14:31:33 2012
@@ -437,52 +437,6 @@ in the given situation.</p>
 
 </div>  <!-- auto-merge -->
 
-<div class="h3" id="incremental-hotcopy">
-<h3>'svnadmin hotcopy' can now operate incrementally (FSFS only)
-  <a class="sectionlink" href="#incremental-hotcopy"
-    title="Link to this section">&para;</a>
-</h3>
-
-<p>The <tt>svnadmin hotcopy</tt> command now supports incremental
-operation, triggered by the new <tt>--incremental</tt> option.</p>
-
-<p>In prior releases of Subversion, <tt>svnadmin hotcopy</tt> refused
-to copy over an existing destination repository, and always copied
-the entire repository. For large repositories, performing a hotcopy
-could take several hours, preventing an efficient backup process.</p>
-
-<p>In incremental hotcopy mode, revision data which has already been
-copied from the source to the destination repository will not be
-copied again. <tt>svnadmin hotcopy --incremental</tt> will only copy
-new revisions, and revisions which have changed in size or had their
-modification time stamp changed since the previous hotcopy operation.</p>
-
-<p>Up to now, <tt>svnsync</tt> or <tt>svnadmin dump --incremental</tt>
-were the only alternatives for incremental repository backup. However,
-these commands need to perform additional processing while transforming
-revision data into an intermediate format before creating revision
-files in the destination repository. Performance of <tt>svnadmin
-hotcopy</tt> is only limited by disk I/O.</p>
-
-<p>Incremental hotcopy is not supported for BDB repositories.
-See <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=4081"
->issue 4081</a> for more information.</p>
-
-<div class="notice">
-<p>Using general-purpose incremental backup tools, such as
-<a href="http://rsync.samba.org">rsync</a>, with Subversion repositories
-is dangerous if the repository can receive commits while the backup
-tool is running. The resulting copy might end up being corrupt because
-general-purpose backup tools do not know anything about consistency
-requirements of Subversion repositories. It is recommended to use
-incremental hotcopy instead. Alternatively, if network support is
-required for the backup procedure, <tt>svnsync</tt> should be used.
-There is also a new <a href="#svnadmin-freeze">svnadmin freeze</a> command
-which allows third-party tools to access a live repository safely.</p>
-</div>
-
-</div>  <!-- incremental-hotcopy -->
-
 <div class="h3" id="gpg-agent">
 <h3>In-memory password caching via GnuPG (<em>Unix client</em>)
   <a class="sectionlink" href="#gpg-agent"
@@ -547,6 +501,52 @@ if a single working copy contains multip
     title="Link to this section">&para;</a>
 </h3>
 
+<div class="h4" id="incremental-hotcopy">
+<h4>'svnadmin hotcopy' can now operate incrementally (FSFS only)
+  <a class="sectionlink" href="#incremental-hotcopy"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>The <tt>svnadmin hotcopy</tt> command now supports incremental
+operation, triggered by the new <tt>--incremental</tt> option.</p>
+
+<p>In prior releases of Subversion, <tt>svnadmin hotcopy</tt> refused
+to copy over an existing destination repository, and always copied
+the entire repository. For large repositories, performing a hotcopy
+could take several hours, preventing an efficient backup process.</p>
+
+<p>In incremental hotcopy mode, revision data which has already been
+copied from the source to the destination repository will not be
+copied again. <tt>svnadmin hotcopy --incremental</tt> will only copy
+new revisions, and revisions which have changed in size or had their
+modification time stamp changed since the previous hotcopy operation.</p>
+
+<p>Up to now, <tt>svnsync</tt> or <tt>svnadmin dump --incremental</tt>
+were the only alternatives for incremental repository backup. However,
+these commands need to perform additional processing while transforming
+revision data into an intermediate format before creating revision
+files in the destination repository. Performance of <tt>svnadmin
+hotcopy</tt> is only limited by disk I/O.</p>
+
+<p>Incremental hotcopy is not supported for BDB repositories.
+See <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=4081"
+>issue 4081</a> for more information.</p>
+
+<div class="notice">
+<p>Using general-purpose incremental backup tools, such as
+<a href="http://rsync.samba.org">rsync</a>, with Subversion repositories
+is dangerous if the repository can receive commits while the backup
+tool is running. The resulting copy might end up being corrupt because
+general-purpose backup tools do not know anything about consistency
+requirements of Subversion repositories. It is recommended to use
+incremental hotcopy instead. Alternatively, if network support is
+required for the backup procedure, <tt>svnsync</tt> should be used.
+There is also a new <a href="#svnadmin-freeze">svnadmin freeze</a> command
+which allows third-party tools to access a live repository safely.</p>
+</div>
+
+</div>  <!-- incremental-hotcopy -->
+
 <div class="h4" id="svnadmin-load">
 <h4>'svnadmin load' now supports the --revision option
   <a class="sectionlink" href="#svnadmin-load"