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

[wuzhouhui at users.sourceforge.net]

Revision: 5657
          http://sourceforge.net/p/svnbook/source/5657
Author:   wuzhouhui
Date:     2018-03-21 14:51:59 +0000 (Wed, 21 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-20 14:08:14 UTC (rev 5656)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-21 14:51:59 UTC (rev 5657)
@@ -4907,6 +4907,7 @@
         或增量转储), 那么仓库管理员可能会把数据库的热拷贝作为每夜例行工作的
         一部分去执行. 这是你的数据—你想怎么保护它们都不为过.</para>
             
+      <!--
       <para>Often, the best approach to repository backups is a
         diversified one that leverages combinations of the methods
         described here.  The Subversion developers, for example, back
@@ -4922,9 +4923,20 @@
         good is a spare tire that has a hole in it?  While all of this
         might not save your hardware from the iron fist of
         Fate,<footnote><para>You know—the collective term for
+            ### TODO
         all of her <quote>fickle fingers.</quote></para></footnote> it
         should certainly help you recover from those trying
         times.</para>
+      -->
+      <para>很多时候, 备份仓库的最佳方式是本节所描述的各种方法的组合. 比如说
+        Subversion 开发人员备份 Subversion 源代码仓库的方式是每晚使用
+        <command>hot-backup.py</command> 和异地的 <command>rsync</command>
+        完成全量备份; 为所有的提交和属性修改通知邮件维护多份归档; 由不同的
+        志愿者使用 <command>svnsync</command> 维护多份仓库镜像. 你的最终
+        方案可能与此类似, 但应该根据你的具体需求维持好易用性与安全性之间的
+        平衡. 无论你怎么做, 应该偶尔检查备份是否可用—如果连备胎都有漏洞,
+        那还怎么用? 虽然这一些都无法避免硬件遭受命运的捶打, 但备份确实能够
+        帮助你从灾难中恢复.</para>
 
     </sect2>