Here's the output of "-v9" for one of my backups. It's quite voluminous, so I've put it in an attachment.
I've also attached a list of the archive dir -- looks to me like the file it's trying to retrieve is already cached.
Thanks,
Dave Cottingham
From: "edgar soldin" <address@hidden>
To: "Discussion of the backup program duplicity" <address@hidden>
Sent: Monday, April 8, 2013 9:05:07 AM
Subject: Re: [Duplicity-talk] Sometimes reads manifest from backup location even though it's in cache -- why?
On 08.04.2013 02:58, address@hidden wrote:
> I see that duplicity will sometimes decide to retrieve a manifest from the remote backup location even though there's a copy in the local cache. Can anyone clarify what circumstances cause this to happen, and why?
>
> Here's why I care. I am backing up to Amazon S3 and using a lifecycle rule to transition everything to Glacier. So, of course, nothing can be retrieved without prior manual intervention. I expected this to work since the local cache has everything duplicity needs, and in fact this worked with nightly backups for over two weeks. But now duplicity fails because it is trying to retrieve the last manifest, even though that file is in the cache.
>
question is why. do you have an extra verbose '-v9' output for us? obfuscate private strings in it and post it here.
..ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
archive-ls