Comment 34 for bug 1039511

I don't upload to Glacier, all this branch does is check to see if a file we are trying to download is on S3 or on Glacier. Because of the way S3 works, we can create rules such as: If file in bucket A is older than X days, move to Glacier. There would have to be a specific modification with how duplicity names files on S3 in order to prevent moving manifests to glacier. I'm not entirely sure of the future implications of changing such a requirement in duplicity for just one backend.

I do agree though, manifests are better kept on S3. What do you mean "paid glacier UPLOAD"? Moving from S3 to glacier comes at no cost. And storing on glacier is significantly cheaper than S3. When the rule "moves" a file from S3 to glacier, it still appears to be in a S3 bucket, but needs to be "restored" before it can be downloaded, so you only pay for storage on glacier and the restoration cost of glacier.