This hint was reported by Marcus Wagner.
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. + |
+
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
+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
[10:53] srsyg01:sources% du -sh ~/backupdir @@ -604,8 +647,8 @@ srwali01:/etc/ccollect/sources# du -sh /mnt/hdbackup/wl6/*