Re: [rdiff-backup-users] logarithmic scheduling

[Rainer Zocholl]

address@hidden(Serge Wroclawski)  13.12.04 11:44


>On 12 Dec 2004, Rainer Zocholl wrote:

>> backups should run "unattended"
>> Every hour a shot is done.
>> That hourly shots should be kept only for 48 hour
>> At the third day
>> one of those 24 shots (say one of 23:00 ) should
>> be kept as "day 0..7", all other "hourly" should be deleted.
>> After a week fridays shot should be kept as "week 1",
>> while all other "days" older than 7 days should be deleted.
>> After 4/5 weeks the last "week" of the previous Months
>> should be renamed to "month x", and all other deleted.
>> After 12 month the last backup of december should become "Year xxx"
>> After 5 years all older year backups should be deleted.

>dirvish does this. Dirvish has many similiarities with rdiff-backup
>but I found rdiff-backup easier to work with (though Dirvish and
>faubackup were close seconds).

>I think faubackup can also do this.

Yes, faubackup can do this and is very easy to configure an
use.
Simply setup the backup destion in teh conf and do a manual
back up.
It has no problems if the source is a symbolic nor if
the destination does not exists. 
(It's very inconvient solved in rdiff-backup when source is a symlink
it only gives an error like "directory does not exist").

I currently don't know if faubackup can link parts of files or
only entire files.

If can do only entire files it would be very inefficient on database 
files, which are very big and change only some few bytes inside
without moving any other. That's what rdiff-backup can handle better, or?


dirvish has the charming feature that's pure perl and seems
to be more effecient over network as it uses rsync, with
allows to be used for non-unix clients too.



>It would indeed be great if rdiff-backup had this.

ACK.


Thanks for the links (faubackup was entire new to me and seems
to be the right tool, as it's available as a debian pkg too.
BTW: It's renamed from "vbackup".)