Re: [Duplicity-talk] Multilevel backup

[edgar . soldin]

hey Peter,

i tried to understand what rdiff-backup does by reading, but do not seem to 
grasp it. being short on time to try it out, could you maybe explain in more 
detail?

thanks ..ede/duply.net

On 23.02.2022 06:36, zga9uhnq4g--- via Duplicity-talk wrote:
> Another way to avoid long backup dependency chains might be to do what rdiff-backup 
> <https://rdiff-backup.net/> does.  It uses reverse diffs so the current backup is just a 
> copy of the source directory, but older increments are "reverse diffs". This makes it 
> always possible to delete the oldest N backups because nothing depends on them.
>
> I've always wondered why duplicity doesn't work that way (encrypted of course), 
> but I assume there is a good reason (which I would love to hear).  I wonder if 
> it could be an option.
>
>      Peter
>
> On 2022-02-22 03:32, edgar.soldin--- via Duplicity-talk 
> duplicity-talk-at-nongnu.org |duplicity-talk| wrote:
> > hi Hakan,
> >
> > comments inline
> >
> > On 21.02.2022 20:39, Håkan T Johansson via Duplicity-talk wrote:
> > > Hello,
> > >
> > > I am wondering if it is possible to do multilevel backup with duplicity?
> > currently no.
> >
> > > (In order to avoid the long backup chains, without having to frequent full new 
> > > backups.)
> > >
> > > If not, I suppose what would be needed would be an option to base some 
> > > incremental backups on not the latest incremental but an earlier one (or the 
> > > full backup).
> > the easiest implementation would probably be a way to base a new chain on a 
> > previous full. maybe via dummy full volume/metadata file, that just points at 
> > the old one.
> >
> > > What I'm contemplating is to e.g. let the first backup every month be 
> > > incremental based on the previous month's first backup.  And the same for weeks 
> > > and days, with the first within each category either based on the previous 
> > > such, or the latest of any category higher, if that is later.
> > >
> > > Together with e.g. remove-older-than 14D, this could give a chain-tree like 
> > > this (each backup based on the previous line, unless there is an arrow):
> > >
> > > full
> > > monthly
> > > monthly
> > > monthly
> > > monthly
> > > ^ weekly
> > > | weekly
> > > | weekly
> > > | weekly
> > > | ^ daily
> > > | | daily
> > > | | daily
> > > | | daily
> > > | | daily
> > > | | daily
> > > | weekly
> > > |   daily
> > > |   daily
> > > monthly
> > >    ^ daily
> > >    | daily
> > >    | daily
> > >    weekly
> > >      daily
> > >      daily
> > >      daily
> > much to complex for my taste. apart from that good luck finding someone to 
> > implement it. feel free to offer to contribute it though :) ..regards 
> > ede/duply.net
> >
> > _______________________________________________
> > Duplicity-talk mailing list
> > Duplicity-talk@nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk