diff options
| author |  gl34 <gl34@web> | 2013-05-30 21:23:02 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-05-30 21:23:02 +0000 |
| commit | a34dc929985c8e3fe5e00a3f35081de369e748f5 (patch) | |
| tree | 3b01a5683e244260f69649e65c429e7074294277 | |
| parent | a347eab5f1ac804ef3cc404b3117225d04e74dac (diff) | |
| -rw-r--r-- | doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn b/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn index 6eca2b64e..d9db436c6 100644 --- a/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn +++ b/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn @@ -1,3 +1,6 @@ I propose to add some functionality to git-annex, to automatically "throttle" the data retrieval from amazon glacier to stay within the daily free retrieval allowance. If someone would need to get his/her files faster, there should be an option to disable this throttling (or even better, specify the retrieval rate). As far as I understand glacier, this could be implemented using range retrievals. In short range retrievals enable you, to only retrieve a part of an archive in glacier. This can be used to only retrieve / request so much data, that you stay within the free retrieval allowance. ( please see [Q: Why would I retrieve only a range of an archive?](http://aws.amazon.com/glacier/faqs/#Why_would_I_retrieve_only_a_range_of_an_archive) ). + + +This would be somewhat similar to the [smart retrieval feature in cloudberry](http://blog.cloudberrylab.com/2012/12/introducing-smart-restore-for-amazon.html) . |