duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] ERROR trying to run remove-older-than


From: edgar . soldin
Subject: Re: [Duplicity-talk] ERROR trying to run remove-older-than
Date: Thu, 23 Aug 2012 20:18:05 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0

you can place the .cache on another filesystem with enough space via 
--archive-dir see manpage  http://duplicity.nongnu.org/duplicity.1.html

you could place all files except of the last chain (latest full and it's 
incremental) into another folder on s3 so only the most recent chain is visible 
to duplicity.

you can use the appropriate remove-* commands explained in the above manpage if 
you are really sure your latest backup  is healthy.

pick your choice.. ede/duply.net


On 23.08.2012 18:38, Kevin Carr wrote:
Ok, that got me further.  Now I am having a problem because of the 
--no-encryption switch, we have not been deleting backups older than 3 months 
for over a year.

Duplicity is trying to put everything in the .cache folder and there is not 
enough space to do so.  Can I just delete the files older than 3 months on s3?

Is there something else I should try?

Thanks for all your help.

On Thu, Aug 23, 2012 at 8:15 AM, SanskritFritz <address@hidden 
<mailto:address@hidden>> wrote:

    On Thu, Aug 23, 2012 at 12:21 PM,  <address@hidden <mailto:address@hidden>> 
wrote:
    > On 22.08.2012 20:41, Tim Riemenschneider wrote:
    >> Am 22.08.2012 15:39, schrieb Kevin Carr:
    >>> I do not see any .gpg files on the s3 bucket.
    >>>
    >>> I see these 2 files for this date.
    >>>
    >>> s3://tndata2/duplicity-full-signatures.20110301T173434Z.sigtar.gz
    >>> 
s3://tndata2/duplicity-new-signatures.20110301T173434Z.to.20110302T114002Z.sigtar.gz
    >>>
    >> Are you doing the backups with "--no-encryption"?
    >> Then you probably need to pass that switch to the remove-older-than as 
well.
    >>
    >> Tim
    >>
    >
    > i second that. use the same parameters as used when creating the backup. you 
could save yourself headache and simply use duply. ..ede/duply.net 
<http://duply.net>

    He is the author of duply so don't take his word ;-)
    But I'm an outsider, and I really really wholeheartedly recommend using 
duply.

    _______________________________________________
    Duplicity-talk mailing list
    address@hidden <mailto:address@hidden>
    https://lists.nongnu.org/mailman/listinfo/duplicity-talk




--
Scott Carr




reply via email to

[Prev in Thread] Current Thread [Next in Thread]