From f9429a50bf0ec42101880e88c4203c29ded38884 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Tue, 17 Jan 2006 13:08:05 +0100 Subject: [PATCH] Added FAQ, more hints --- doc/ccollect.html | 59 ++++++++++++++++++++++++++++++++++++++++------- doc/ccollect.text | 48 ++++++++++++++++++++++++++++++++++++-- 2 files changed, 97 insertions(+), 10 deletions(-) diff --git a/doc/ccollect.html b/doc/ccollect.html index 91fb91c..bc6cee6 100644 --- a/doc/ccollect.html +++ b/doc/ccollect.html @@ -262,8 +262,8 @@ div.exampleblock-content {

ccollect - Installing, Configuring and Using

Nico Schottelius
<nico-linux-ccollect__@__schottelius.org>
-version 0.2, -2005-01-13 +version 0.2.2, +for ccollect 0.2, Initial Version 2005-01-13
@@ -523,11 +523,54 @@ they will still be transferred!

This hint was reported by Marcus Wagner.

5.3. Re-using already created rsync-backups

-

mkdir intervall.0 ; mv * intervall;

+

If you used rsync directly before you use ccollect, you can +use this old backup as initial backup for ccollect: You +simply move it into a subdirectory named "intervall.0".

+

Example:

+
+
+
backup:/home/backup/web1# ls
+bin   dev  etc   initrd  lost+found  mnt  root  srv  usr  vmlinuz
+boot  doc  home  lib     media       opt  sbin  tmp  var  vmlinuz.old
+
+backup:/home/backup/web1# mkdir daily.0
+
+# ignore error about copying to itself
+backup:/home/backup/web1# mv * daily.0 2>/dev/null
+
+backup:/home/backup/web1# ls
+daily.0
+
+

Now you could use /home/backup/web1 as the destination for the backup.

+
+ + + +
+
Note
+		 +

Do not name the first backup something like "daily.initial", but use +the "0" (or some very low number, at least lower than the current year) +as extension. ccollect uses sort to find the latest backup. ccollect +itself uses intervall.YEAR-MONTH-DAY-HOUR:MINUTE.PID. This notation will +always be before "daily.initial", as numbers are earlier in the list +which is produced by sort. So, if you have a directory named "daily.initial", +ccollect will always diff against this backup and transfer and delete +files which where deleted in previous backups. This means you simply +waste resources, but your backup will be complete.

+
-

6. Examples

+
+

6. F.A.Q.

-

6.1. A backup host configuration from scratch

+

6.1. What happens, if one backup is broken / 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.

+

The next time you use ccollect, it will transfer the missing files

+
+

7. Examples

+
+

7.1. A backup host configuration from scratch

srwali01:~# mkdir /etc/ccollect
@@ -582,7 +625,7 @@ srwali01:/etc/ccollect/sources/srwali03# echo 'root@10.103.2.3:/' > source
 srwali01:/etc/ccollect/sources/srwali03# ln -s /mnt/hdbackup/srwali03 destination
 srwali01:/etc/ccollect/sources/srwali03# mkdir /mnt/hdbackup/srwali03
-

6.2. Using hard-links requires less disk space

+

7.2. Using hard-links requires less disk space

[10:53] srsyg01:sources% du -sh ~/backupdir
@@ -604,8 +647,8 @@ srwali01:/etc/ccollect/sources# du -sh /mnt/hdbackup/wl6/*
diff --git a/doc/ccollect.text b/doc/ccollect.text index 73518a5..9bdf19b 100644 --- a/doc/ccollect.text +++ b/doc/ccollect.text @@ -1,7 +1,7 @@ ccollect - Installing, Configuring and Using ============================================ Nico Schottelius -v0.2, 2005-01-13 +0.2.2, for ccollect 0.2, Initial Version from 2005-01-13 :Author Initials: NS (pseudo) incremental backup @@ -276,7 +276,51 @@ This hint was reported by Marcus Wagner. Re-using already created rsync-backups ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -mkdir intervall.0 ; mv * intervall; +If you used `rsync` directly before you use `ccollect`, you can +use this old backup as initial backup for `ccollect`: You +simply move it into a subdirectory named "'intervall'.0". + +Example: +------------------------------------------------------------------------------- +backup:/home/backup/web1# ls +bin dev etc initrd lost+found mnt root srv usr vmlinuz +boot doc home lib media opt sbin tmp var vmlinuz.old + +backup:/home/backup/web1# mkdir daily.0 + +# ignore error about copying to itself +backup:/home/backup/web1# mv * daily.0 2>/dev/null + +backup:/home/backup/web1# ls +daily.0 +------------------------------------------------------------------------------- +Now you could use /home/backup/web1 as the `destination` for the backup. + +[NOTE] +=============================================================================== +Do *not* name the first backup something like "daily.initial", but use +the "*0*" (or some very low number, at least lower than the current year) +as extension. `ccollect` uses `sort` to find the latest backup. `ccollect` +itself uses 'intervall.YEAR-MONTH-DAY-HOUR:MINUTE.PID'. This notation will +*always* be before "daily.initial", as numbers are earlier in the list +which is produced by `sort`. So, if you have a directory named "daily.initial", +`ccollect` will always diff against this backup and transfer and delete +files which where deleted in previous backups. This means you simply +waste resources, but your backup will be complete. +=============================================================================== + + +F.A.Q. +------ + +What happens, if one backup is broken / 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. + +The next time you use `ccollect`, it will transfer the missing files + Examples --------