jfut/ccollect
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix more typos.

Browse source 
And explain better what happens if one backup is broken.
This commit is contained in:
Nico Schottelius 2006-02-23 09:51:39 +01:00
parent a28fae4a0b
commit 482913f86d
2 changed files with 16 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/ccollect.html
View file

@ -397,9 +397,9 @@ human readable format before and after the whole backup process:</p>
<div class="listingblock"> <div class="listingblock">
<div class="content"> <div class="content">
<pre><tt>[13:00] hydrogenium:~# mkdir -p /etc/ccollect/defaults/ <pre><tt>[13:00] hydrogenium:~# mkdir -p /etc/ccollect/defaults/
[13:00] hydrogenium:~# echo '!/bin/sh' &gt; /etc/ccollect/defaults/pre_exec [13:00] hydrogenium:~# echo '#!/bin/sh' &gt; /etc/ccollect/defaults/pre_exec
[13:01] hydrogenium:~# echo '' &gt;&gt; /etc/ccollect/defaults/pre_exec [13:01] hydrogenium:~# echo '' &gt;&gt; /etc/ccollect/defaults/pre_exec
[13:01] hydrogenium:~# echo 'df -h' &gt;&gt; /etc/ccollect/defaults/pre_exec [13:01] hydrogenium:~# echo 'df -h' &gt;&gt; /etc/ccollect/defaults/pre_exec
[13:01] hydrogenium:~# chmod 0755 /etc/ccollect/defaults/pre_exec [13:01] hydrogenium:~# chmod 0755 /etc/ccollect/defaults/pre_exec
[13:01] hydrogenium:~# ln -s /etc/ccollect/defaults/pre_exec /etc/ccollect/defaults/post_exec</tt></pre> [13:01] hydrogenium:~# ln -s /etc/ccollect/defaults/pre_exec /etc/ccollect/defaults/post_exec</tt></pre>
</div></div> </div></div>
@ -837,7 +837,7 @@ the hardlinks allocate.</p>
<div id="footer"> <div id="footer">
<div id="footer-text"> <div id="footer-text">
Version 0.3.2<br /> Version 0.3.2<br />
Last updated 06-Feb-2006 08:20:48 CEST Last updated 23-Feb-2006 09:42:20 CEST
</div> </div>
</div> </div>
</body> </body>

18
doc/ccollect.text
View file

@ -1,7 +1,7 @@
ccollect - Installing, Configuring and Using ccollect - Installing, Configuring and Using
============================================ ============================================
Nico Schottelius <nico-linux-ccollect__@__schottelius.org> Nico Schottelius <nico-linux-ccollect__@__schottelius.org>
0.3.2, for ccollect 0.3.2, Initial Version from 2005-01-13 0.3.3, for ccollect 0.3.2, Initial Version from 2006-01-13
:Author Initials: NS :Author Initials: NS
(pseudo) incremental backup (pseudo) incremental backup
@ -153,7 +153,7 @@ Additionally a source may have the following files:
- `summary` create a transfer summary when `rsync` finished - `summary` create a transfer summary when `rsync` finished
- `exclude` exclude list for `rsync`. newline ('\n') seperated list. - `exclude` exclude list for `rsync`. newline ('\n') seperated list.
- `rsync_options' extra options to pass to `rsync` - `rsync_options` extra options to pass to `rsync`
- `pre_exec` program to execute before backuping this source - `pre_exec` program to execute before backuping this source
- `post_exec` program to execute after backuping this source - `post_exec` program to execute after backuping this source
@ -187,7 +187,8 @@ Detailled description of "source"
For instance 'backup_user@foreign_host:/home/server/video'. For instance 'backup_user@foreign_host:/home/server/video'.
To use the `rsync` protocol without the `ssh`-tunnel, use To use the `rsync` protocol without the `ssh`-tunnel, use
'rsync::USER@HOST/SRC'. For more information have a look at `rsync`(1). 'rsync::USER@HOST/SRC'. For more information have a look at the manpage
of `rsync`,`rsync`(1).
Detailled description of "verbose" Detailled description of "verbose"
@ -438,10 +439,15 @@ F.A.Q.
What happens, if one backup is broken or empty? What happens, if one backup is broken or empty?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let us assume, that one backup failed (connection broke or hard disk had Let us assume, that one backup failed (connection broke or the source
some failures). So we've one backup in our history, which is incomplete. hard disk had some failures). So we've one backup in our history,
which is incomplete.
The next time you use `ccollect`, it will transfer the missing files The next time you use `ccollect`, it will transfer the missing files.
This leads to
- more transferred files
- much greater disk space usage, as no hardlinks can be used
When backing up from localhost the destination is also included. Is this a bug? When backing up from localhost the destination is also included. Is this a bug?