[svnbook] r5653 committed - branches/1.8/zh/book/ch05-repository-admin.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5653
          http://sourceforge.net/p/svnbook/source/5653
Author:   wuzhouhui
Date:     2018-03-16 11:24:26 +0000 (Fri, 16 Mar 2018)
Log Message:
-----------
1.8/zh: translation of chapter 5 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch05-repository-admin.xml

Modified: branches/1.8/zh/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-14 14:38:44 UTC (rev 5652)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-16 11:24:26 UTC (rev 5653)
@@ -4756,14 +4756,15 @@
         执行 <command>hot-backup.py</command>, 从而实现每晚运行一次 (或
         管理员认为合适的其他时间间隔) 脚本.</para>
 
+      <!--
       <para>Some administrators use a different backup mechanism built
         around generating and storing repository dump data.  We
         described in <xref linkend="svn.reposadmin.maint.migrate" />
         how to use <command>svnadmin dump</command> with
-        the <option>--incremental</option> option to perform an
+        the <option>- -incremental</option> option to perform an
         incremental backup of a given revision or range of revisions.
         And of course, you can achieve a full backup variation of this
-        by omitting the <option>--incremental</option> option to that
+        by omitting the <option>- -incremental</option> option to that
         command.  There is some value in these methods, in that the
         format of your backed-up information is flexible—it's
         not tied to a particular platform, versioned filesystem type,
@@ -4776,6 +4777,19 @@
         up by a nonoverlapping, incremental dump generation.  For
         these reasons, we recommend against relying solely on
         dump-based backup approaches.</para>
+      -->
+      <para>围绕仓库转储数据的生成与存放, 有些管理员会使用不同的备份方法.
+        在 <xref linkend="svn.reposadmin.maint.migrate" /> 我们介绍了如何
+        使用带有选项 <option>--incremental</option> 的 <command>svnadmin
+          dump</command>, 在给定的版本号或版本号范围内执行增量备份. 当然,
+        也可以忽略选项 <option>--incremental</option>, 实现一个完全备份.
+        使用仓库转储数据的好处是这种备份信息的格式非常灵活—它与特定
+        的平台, 仓库文件系统类型, Subversion 的版本及其所使用的函数库都是
+        无关的. 但灵活性也带来了一定的开销, 就是需要较长的时候才能完全恢复
+        数据—每当有一个新的版本号提交时, 时间就会变得更长一点. 另外,
+        和其他备份方法相比, 如果修改了已经备份过的版本号的版本号属性, 这些
+        修改将不会体现在增量的转储数据中. 由于这些原因, 我们建议读者不要单独
+        依靠基于转储的备份策略.</para>
 
       <para>Beginning with Subversion 1.8, <command>svnadmin hotcopy</command>
         accepts <option>--incremental</option> option and supports incremental