Dan Pitts suggested:
FullPeriod=27.9
incrperiod=.9
# this should add up to 27 days worth
incrlevels=[2,2,2,2,2,2,1,2,2,2,2,2,2,1,2,2,2,2,2,2,1,2,2,2,2,2,2]
incrkeepcount= however many you want
And I agree but I think the incrlevels repeat so you might need only the first
6 or so 2's and a 1. Les is suggesting something like a Full every week and
just keep four fulls and week's worth of incrementals. That also seems like a
good idea if the "full" is essentially an incremental if you include the
pooling. I'll give the latter a go.
Thanks for the tips,
Chris
Les Mikesell wrote:
> Christopher Derr wrote:
>> I've been reading the docs on incrementals and it isn't 100% clear to
>> me how to use the directives for something like:
>>
>> One full a month
>> A level 1 incremental at the end of each week
>> level 2 incrementals between
>>
>> Goal: To have backups going back one month with a fairly minimal use
>> of storage space.
>>
>> I'd appreciate a kick in the right direction for a solution similar
>> to this using the FullPeriod, IncrPeriod, IncrKeepcnt, and IncrLevels.
>
> Before you start down this path, be sure you understand that storing
> multiple fulls doesn't take up a lot more space than incrementals
> since all identical copies of a file are pooled. Also, with the tar
> and smb methods you can miss files in incrementals if they are copied
> in ways that preserve old timestamps.
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
