I guess my actual question, which magic number determines how far back
your backups go? Is it the FullAgeMax?
--
-a
"Ideally, a code library must be immediately usable by naive
developers, easily customized by more sophisticated developers, and
readily extensible by experts." -- L. Stein
On Apr 20, 2009, at 11:01 AM, Schley Andrew Kutz wrote:
> Thank for your answers regarding the space issue, as well as the
> differences between l0's and l1's. What exactly do you mean when you
> say "average change rate"? Right now BPC is set at the defaults --
> to keep 1 full with an age of 90 days.
>
> --
> -a
>
> "Ideally, a code library must be immediately usable by naive
> developers, easily customized by more sophisticated developers, and
> readily extensible by experts." -- L. Stein
>
> On Apr 20, 2009, at 10:42 AM, Les Mikesell wrote:
>
>> Schley Andrew Kutz wrote:
>>> Please pardon my ignorance. I have always been dense when it comes
>>> to
>>> backups, and I am hoping that someone can simply tell me the
>>> appropriate schedule for what I want to do. I basically want to
>>> mimic
>>> Apple's Time Machine settings. I want an initial full backup and
>>> then
>>> simply a backup of changed files every X amount of time (their
>>> interval is hourly, mine would be daily). I don't want old backups
>>> deleted until the drive begins to run out of space. Time Machine
>>> keeps
>>> hourly backups for 24 hours and then rolls them into a 24 hour
>>> backup.
>>> It keeps 7 24 hour back-ups (a weeks worth), and then rolls them
>>> into
>>> weekly backups. Is this possible with BackupPC?
>>
>> Backuppc won't adapt to the available space automatically other
>> than not
>> starting runs if you have less that 5% of the disk free. However,
>> since
>> it only needs additional space for new/changed files, once you have
>> an
>> idea of the average change rate you can set the number of full
>> backups
>> to keep accordingly.
>>
>>> Right now it has the default settings. Also, as I understand
>>> things, a
>>> BackupPC full backup is only the files that have changed since the
>>> last full backup. My question is then why do incremental backups,
>>> why
>>> not just always do full backups. Is it because of the method to
>>> determine if a file has changed? Timestamp vs. block checksum in
>>> Rsync
>>> for example?
>>
>> Yes, with rsync there is the difference in time for the checksum
>> comparison for fulls - and on the server side, fulls also rebuild the
>> directory link trees to be used for the next run.
>>
>> --
>> Les Mikesell
>> lesmikesell AT gmail DOT com
>>
>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> 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/
>
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
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/
|
