Re: [Duplicity-talk] Sometimes reads manifest from backup location even though it's in cache -- why?

[Kuang-che Wu]

On Mon, Apr 08, 2013 at 12:58:13AM +0000, 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. 
> 
> Thanks for any help, 
> Dave Cottingham 
> 

This is my patch to address this issue.

1. in _boto_single.py, I moved these two lines 
        key = self.key_class(self.bucket)
        key.key = self.key_prefix + remote_filename
into loop, otherwise it won't retry when fail.
(this is a bug)

2. detect 'InvalidObjectState' and ignore it silently.
InvalidObjectState means the data you want to retrieve is in glacier,
not in S3.
(this is workaround)

patch-duplicity-boto.txt
Description: Text document

pgpva2QJ5WV0q.pgp
Description: PGP signature