Comment 3 for bug 1039511

I see no reason to keep incremental backups off of Glacier. What advantage does this grant you?

Glacier would be a great backend to implement, lower pricing than RRS (~11% the cost per GB for the first TB) and the durability of standard S3 storage. Also, default automatic AES encryption further helps to keep our data secure (although to be fair, you can do this in S3 as well).

I wonder if it will take longer to upload though. It doesn't return a "SUCCESS" on upload until it replicates out to all data centers. May this be an excuse to revisit the threading found within duplicity and increase it to a specified number of upload thread handlers? Amazon's best practice recommends that you try and upload multiple objects to its data centers at once since a single connection may be rate limited depending on how often you use it and which server you connect to. I would think 3-6 upload threads could best saturate most small business upload connections.