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

Implemented very_verbose and changed standard behaviour. Also added some

Browse source 
more documentation
This commit is contained in:
Nico Schottelius 2006-01-22 10:40:40 +01:00
commit f99404a04a
3 changed files with 34 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/ccollect.html
View file

@ -263,7 +263,7 @@ div.exampleblock-content {
<span id="author">Nico Schottelius</span><br />
<span id="email"><tt>&lt;<a href="mailto:nico-linux-ccollect__@__schottelius.org">nico-linux-ccollect__@__schottelius.org</a>&gt;</tt></span><br />
<span id="revision">version 0.2.2,</span>
for ccollect 0.2, Initial Version 2005-01-13
for ccollect 0.2, Initial Version from 2005-01-13
</div>
<div id="preamble">
<div class="sectionbody">
@ -563,10 +563,17 @@ waste resources, but your backup will be complete.</p>
</div>
<h2>6. F.A.Q.</h2>
<div class="sectionbody">
<h3>6.1. What happens, if one backup is broken / empty?</h3>
<h3>6.1. What happens, if one backup is broken or empty?</h3>
<p>Let us assume, that one backup failed (connection broke or hard disk had
some failures). So we've one backup in our history, which is incomplete.</p>
<p>The next time you use <tt>ccollect</tt>, it will transfer the missing files</p>
<h3>6.2. When backing up from localhost the destination is also included. Is this a bug?</h3>
<p>No. <tt>ccollect</tt> passes your source definition directly to <tt>rsync</tt>. It
does not try to analyze it. So it actually does not know if a source
comes from local harddisk or from a remote server. And it does not want
to. When you backup from the local harddisk (which is perhaps not
even a good idea when thinking of security) add the <tt>destination</tt>
to <em>source/exclude</em>. (Daniel Aubry reported this problem)</p>
</div>
<h2>7. Examples</h2>
<div class="sectionbody">
@ -648,7 +655,7 @@ srwali01:/etc/ccollect/sources# du -sh /mnt/hdbackup/wl6/*
<div id="footer">
<div id="footer-text">
Version 0.2.2<br />
Last updated 17-Jan-2006 12:59:55 CEST
Last updated 21-Jan-2006 11:37:48 CEST
</div>
</div>
</body>

15
doc/ccollect.text
View file

@ -313,8 +313,8 @@ waste resources, but your backup will be complete.
F.A.Q.
------
What happens, if one backup is broken / empty?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
What happens, if one backup is broken or empty?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let us assume, that one backup failed (connection broke or hard disk had
some failures). So we've one backup in our history, which is incomplete.
@ -322,6 +322,17 @@ 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
When backing up from localhost the destination is also included. Is this a bug?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No. `ccollect` passes your source definition directly to `rsync`. It
does not try to analyze it. So it actually does not know if a source
comes from local harddisk or from a remote server. And it does not want
to. When you backup from the local harddisk (which is perhaps not
even a good idea when thinking of security) add the `destination`
to 'source/exclude'. (Daniel Aubry reported this problem)
Examples
--------