Comment 13 for bug 1039511

Ok, I see what I missed. I've taken into account the data transfer and request fee, but not the excess-retrieval fee which is calculated based on the peak download rate.

That can be mitigated by a) using an EC2 server as a go between (possibly free in the first year, but may not be a cheaper option after that), and b) rate-limiting the download.

It might be nice if a duplicity implementation had some kind of smart rate-limiter to solve the problem, but my point above about storage savings still stands.