Hello everybody,

I've written a script for backing up my desktop computer at home. I've got a few directories I find very important and the data in there also changes a lot (like the directory which contains my e-mail). So I backup that every hour. This script creates increments of the directory and saves old increments for 2 days.
But my desktop isn't turned on 24/7. I turn it off every night.
When I turn it back on, then my script runs a backup again. And when it runs rdiff-backup --remove-older-than 2D "/backup/snapshots/home/cybertinus/mail" it finds a lot of old increments. I get something like the following error:

"Starting backup of /home/cybertinus/mail at Fri Jun 12 10:00:32 CEST 2009
Fatal Error: Found 5 relevant increments, dated:
Wed Jun 10 01:00:51 2009
Wed Jun 10 06:00:43 2009
Wed Jun 10 07:00:53 2009
Wed Jun 10 08:00:51 2009
Wed Jun 10 09:00:44 2009
If you want to delete multiple increments in this way, use the --force.
Done backing up /home/cybertinus/mail at Fri Jun 12 10:00:49 CEST 2009"

(the first and last line of that message are generated by my script ;) )

So I must use --force manually then. I don't fancy doing this manual action every day for multiple directories. I've created a cronjob to get this done automatically every hour with a reason ;).

So my question: can it do any harm when I change the command in the cronjob to a version with --force in it by default? I've found the warning in the manpage, but I can't really tell if it really isn't smart to use it automatically. Every time I used it manually it ran without problems.

Thnx for your reply's :).

Regards, Cybertinus


_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Reply via email to