Amazon Glacier

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Amazon Glacier
200px
Web address aws.amazon.com/glacier/
Commercial? Yes
Type of site
 Online backup service
Registration Required
Available in English
Owner Amazon.com
Launched August 21, 2012
Current status Active

Amazon Glacier is an online file storage web service that provides storage for data archiving and backup.[1]

Glacier is part of the Amazon Web Services suite of cloud computing services, and is designed for long-term storage of data that is infrequently accessed and for which retrieval latency times of 3 to 5 hours are acceptable. Storage costs are a consistent $0.007 per gigabyte per month, which is substantially cheaper than Amazon's own Simple Storage Service (S3).[2]

Amazon hopes this new service will move businesses from on-premises tape backup drives to cloud-based backup storage.[3]

Storage

ZDNet says, that according to private e-mail, Glacier runs on "inexpensive commodity hardware components".[3] In 2012, ZDNet quoted a former Amazon employee as saying that Glacier is based on custom low-RPM hard drives attached to custom logic boards where only a percentage of a rack's drives can be spun at full speed at any one time.[4][5] (Similar technology is also used by Facebook.)[6]

There is some belief amongst users that the underlying hardware used for Glacier storage is tape-based, owing to the fact that Amazon has positioned Glacier as a direct competitor to tape backup services (both on-premises and cloud-based).[7] This confusion is exacerbated by the fact that Glacier has archive retrieval delays (3–5 hours before archives are available) similar to that of tape-based systems and a pricing model that discourages frequent data retrieval.[8]

The Register claimed that Glacier runs on Spectra T-Finity tape libraries with LTO-6 tapes.[9][10] Others have conjectured Amazon using off-line shingled magnetic recording hard drives, multi-layer Blu-ray optical discs, or an alternative proprietary storage technology.[11]

Cost

While an unlimited amount of data can be uploaded for storage, the pricing structure for downloading data (retrieval) is far more complex. Getting data out of Glacier is a two-step process. The first step is to retrieve the data from Glacier staging area, subject to Glacier retrieval pricing. The next step is to actually download (transfer) the data. While Glacier advertises a free 5% per month allowance, this 5% is spread out evenly across the number of hours in a month for a 0.006944% free retrieval per hour (assuming a 30-day month). Exceeding the hourly allowance (aka peak hourly rate) at any time results in a peak retrieval overage charge that gets multiplied by the number of hours in a month.[12]

In the more practical terms, Glacier users need to break up any sizeable retrievals across the longest period of time practical to eliminate or minimize overage charges. Developers who are planning to implement Glacier support in their applications also need to implement a mechanism for spreading out data retrieval over a long period of time, and to be extremely careful with their testing: a simple mistake or misunderstanding can easily result in a massive bill. In one example, a user stored 15GB of data in Glacier, retrieved 693MB for testing, and ended up being charged for 126GB due to retrieval rate calculation.[13]

Uploading data to Glacier is free, but downloading data from Glacier may be charged.[14] This technically puts kind of a "time bomb" into data stored. Data transfer to the EC2 cloud in the same region is free, while data transfer between AWS regions is charged with $0.02 per GB ($0.09 per GB if data is downloaded from Tokyo region). Data transfer from Glacier to the Internet is free up to 1 GB per month, after which a sliding scale fee starts at $0.12 per GB. Data stored in Glacier but which is deleted after being stored for a period of less than 3 months incurs a charge of $0.03 per GB, a move designed to discourage the service's use in cases where Amazon's other storage offerings (e.g. S3) are more appropriate for real-time access.

Glacier is up to 66% cheaper than AWS S3, which in the past was the only way of archiving on the AWS cloud.

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ http://arstechnica.com/information-technology/2015/11/to-go-green-facebook-puts-petabytes-of-cat-pics-on-ice-and-likes-windfarming/
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ http://www.wired.com/2012/08/glacier/

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Amazon_Glacier&oldid=715396364"