Re: [Duplicity-talk] Deletion of old backup sets

[Florian Lindner]

Am 15.03.2009 um 13:36 schrieb Kenneth Loafman:

> Florian Lindner wrote:
> > Hello,
> >
> > I'm using duplicity called from cron to backup my server data each  
> > night
> > to another server using SSH.
> >
> > There are backup set(s) at time(s):
> > Wed Jan  7 12:39:09 2009
> > [... virtually every day between these dates ...]
> > Thu Feb 12 06:26:14 2009
> > Which can't be deleted because newer sets depend on them.
> > No old backup sets found, nothing deleted.
> >
> > For removal duplicity is called: duplicity remove-older-than 1M
> > $TARGET/home
> >
> > Does the message means that the entire backup set is not deleted?  
> > Thus
> > if a set contains one file which has not been changed, the entire set
> > won't be deleted? I rather thought that only the files which newer  
> > sets
> > depend on are kept not the entire set.
>
> It looks like you're only running incremental backups.  Duplicity does
> not force a full backup on a regular basis, its up to you.  If this is
> one full backup, followed by many incremental backups, then there is  
> no
> way to delete anything until after you have done the next full backup.

Hello,

I need to resurrect this thread...

I've done:

        duplicity full --sign-key "F1917066" --encrypt-key  
"F1917066" /etc $TARGET/etc
        duplicity remove-older-than 1M $TARGET/etc

The last command still outputs a long list of backup sets that can't  
be deleted because newer sets depend on them. These sets are dating  
back till january, older than one month.

Any idea why duplicity won't touch them though I've done a full backup?

Regards,

Florian