> What I would find useful is a rolling incremental backup that is not
> dependant on a full backup - yea I know that sounds silly!
>
> This would allow a backup to disk solution (like on a SAN), where the last
> few months worth of backups can be kept on a rolling basis, and
> automatically deleted if older than X months.
>
> Some configuration variable [perhaps $Conf{LastIncrFull}], that would do an
> incremental fill [like $Conf{IncrFill}] on the oldest incremental and treat
> it as a full backup?
Why not just use $Conf{IncrFill}? It would achieve exactly the same
thing, only that the incremental is filled immediately after backup, not
before it is expiring.
I don't see how this would allow a SAN to delete something - every file
is linked to the global pool which needs to be on the same file system
as the backup itself. You can achieve the same thing by just backing up
to a file system stored on SAN and letting BackupPC handle the
expiration. What are you trying to achieve, exactly (maybe I don't
understand the term "on a rolling basis"?)
Bye,
Tino.
--
"What we nourish flourishes." - "Was wir nähren erblüht."
www.lichtkreis-chemnitz.de
www.craniosacralzentrum.de
-------------------------------------------------------------------------
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-devel mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
