Matthias Meyer wrote at about 13:04:01 +0100 on Saturday, March 12, 2011:
> I've implemented some changes more than a year ago.
> I've run the changed BackupPC within a production environment since a year.
> My patch contains:
> - store each interrupted backup as a partial backup and makes it possible
> to configure how much partials should be stored as a maximum
> - make the first backup of a year as a full backup and makes it possible to
> configure how much of this yearly backups can be stored
>
> Therefore the following configuration items where be added:
> $Conf{FullCntYearly}
> $Conf{useEveryPartial}
> $Conf{PartialAgeMax}
>
> See BackupPC.html for a detailed description.
Sounds great!
Does the patch work against 3.2.0 which is the current version and of
course includes other good patches?
Also, I have always wanted to have the ability to flag individual
backups to be saved and to escape the pruning logic (if an incremental
were so tagged then also the lower level incrementals and
corresponding full would be saved).
The easiest way is to rename the backups so that they don't get
detected by the deletion algorithm but then they don't show up in the
web interface and you lose the backupinfo data.
It would be nice to have an official scheme to support this. Say, by
adding a ".save" suffix to a backup which would tell BackupPC to still
view it as a backup but not to delete it.
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
