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

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Mon Mar 12 09:00:58 CDT 2018


Revision: 5651
          http://sourceforge.net/p/svnbook/source/5651
Author:   wuzhouhui
Date:     2018-03-12 14:00:57 +0000 (Mon, 12 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-07 14:31:03 UTC (rev 5650)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-12 14:00:57 UTC (rev 5651)
@@ -4650,6 +4650,7 @@
       -->
       <title>仓库备份</title>
 
+      <!--
       <para>Despite numerous advances in technology since the birth of
         the modern computer, one thing unfortunately rings true with
         crystalline clarity—sometimes things go very, very
@@ -4659,7 +4660,13 @@
         administrator.  And so we arrive at a very important
         topic—how to make backup copies of your repository
         data.</para>
+      -->
+      <para>自现代计算机诞生以来, 不管出现了多么先进的技术, 有一点总是挥之不
+        去—有时候, 事情会变得非常糟糕. 即使是最小心翼翼的管理员, 也不得
+        不面对断电, 网络故障, 内存与硬盘损坏. 因此本节的主题是如何备份仓库数
+        据.</para>
 
+      <!--
       <para>There are two types of backup methods available for
         Subversion repository administrators—full and
         incremental.  A full backup of the repository involves
@@ -4671,6 +4678,12 @@
         backups are lesser things:  backups of only the portion of the
         repository data that has changed since the previous
         backup.</para>
+      -->
+      <para>对于 Subversion 仓库管理员来说, 有两种备份策略—全量备份与
+        增量备份. 全量备份涉及到在一个操作中记录所有的信息, 这些信息可以在
+        灾难发生后, 重新构造出原来的仓库. 通常意味着复制整个仓库目录 (包括
+        后端存储 Berkeley DB 或 FSFS 的数据). 增量备份每次记录的数据量相对
+        较少: 它只备份上一次备份以来, 发生变化的仓库数据.</para>
 
       <para>As far as full backups go, the naïve approach might seem
         like a sane one, but unless you temporarily disable all other




More information about the svnbook-dev mailing list