[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Purging, purge-full, not working?
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Purging, purge-full, not working? |
Date: |
Sun, 24 Aug 2014 14:11:08 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 |
probably this one
New in v0.6.21 (2013/01/23)
---------------------------
...
* Merged in lp:~mterry/duplicity/delete-new-sig-in-cache
- In duplicity 0.6.20, we fixed bug 1031269. This means that we no longer
leave sig files on the remote location. Leaving sig files on the remote
location also caused a bug with deleting cache files. Code used to leave
remote new-sig but delete the locale cache new-sig; this meant that we would
keep downloadoing the new-sig all the time from remote. We had worked around
that by just not deleting the new-sig in the cache, which was sort of the
wrong side of that problem to tackle. Now that we handle the remote
new-sigs better (by deleting them), I don't think we need this code anymore.
Patch by address@hidden
On 22.08.2014 17:28, Karl Buckland wrote:
> Hi,
>
> I've installed 0.6.24 and that has resolved the issue. I can only assume that
> there's some sort of problem with 0.6.18. I'll have to compile 0.6.24 for the
> other servers.
>
> Thanks for your help.
>
> Karl
>
>
> On 22 August 2014 13:23, <address@hidden <mailto:address@hidden>> wrote:
>
> On 22.08.2014 14:07, Karl Buckland wrote:
> > Hi,
> >
> > Thanks for your help so far.
> >
> > The preview command shows that the the time argument does change. That
> would indicate that the issue is with Duplicity instead?
> >
> > Eg:
> > duply chronos purge --preview
> >
> > TMPDIR='/tmp' PASSPHRASE='x' AWS_ACCESS_KEY_ID='x'
> AWS_SECRET_ACCESS_KEY='X' duplicity remove-older-than 3M --name duply_chronos
> --verbosity '4' --full-if-older-than 1M --volsize 250
> 's3://s3-eu-west-1.amazonaws.com/X/Y <http://s3-eu-west-1.amazonaws.com/X/Y>
> <http://s3-eu-west-1.amazonaws.com/X/Y>
> >
> > duply chronos purge 30D --preview
> >
> > TMPDIR='/tmp' PASSPHRASE='X' AWS_ACCESS_KEY_ID='X'
> AWS_SECRET_ACCESS_KEY='X' duplicity remove-older-than 30D --name
> duply_chronos --verbosity '4' --full-if-older-than 1M --volsize 250
> 's3://s3-eu-west-1.amazonaws.com/X/Y <http://s3-eu-west-1.amazonaws.com/X/Y>
> <http://s3-eu-west-1.amazonaws.com/X/Y>'
> >
> > If I upgrade Duplicity, am I safe to use my existing backups? My
> assumption would be 'no' and that I need to make fresh backups with the new
> Duplicity. If that's the case, which isn't a problem, then my issue will have
> to go on hold for a few days at least until I have a few days worth of
> backups to play with the purge functions again.
>
>
> duplicity data format hasn't changed for a long time. so no worries there.
>
> wrt. your original issue. please update and see if the error persists. if
> so, let's dig in deeper.. ede/duply.net <http://duply.net>
>
>
- [Duplicity-talk] Purging, purge-full, not working?, Karl Buckland, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, edgar . soldin, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, Karl Buckland, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, edgar . soldin, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, Karl Buckland, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, edgar . soldin, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?, Karl Buckland, 2014/08/22
- Re: [Duplicity-talk] Purging, purge-full, not working?,
edgar . soldin <=