diff --git a/ccollect.sh b/ccollect.sh index 4903c2f..b655189 100755 --- a/ccollect.sh +++ b/ccollect.sh @@ -367,10 +367,9 @@ while [ "$i" -lt "$no_shares" ]; do if [ "$?" -ne 0 ]; then echo "rsync reported an error. The backup may be broken (see rsync errors)" - exit 1 fi - echo "$(date) Successfully finished backup" + echo "$(date) Finished backup" # # post_exec diff --git a/doc/ccollect.html b/doc/ccollect.html index 1133403..fae487c 100644 --- a/doc/ccollect.html +++ b/doc/ccollect.html @@ -262,8 +262,8 @@ div.exampleblock-content {
-rsync_options' extra options to pass to `rsync +rsync_options extra options to pass to rsync
source describes a rsync compatible source (one line only).
For instance backup_user@foreign_host:/home/server/video. 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).verbose tells ccollect that the log should contain verbose messages.
If this file exists in the source specification -v will be passed to rsync.
@@ -701,9 +702,23 @@ an already written scriptLet 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.
-The next time you use ccollect, it will transfer the missing files
+Let us assume, that one backup failed (connection broke or the source +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. +This leads to
++more transferred files +
++much greater disk space usage, as no hardlinks can be used +
+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 @@ -836,8 +851,8 @@ the hardlinks allocate.