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