{"_id":"56d96baddd90610b0027084d","version":{"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","__v":37,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055","58ef66d88646742f009a0216","58f5d52d7891630f00fe4e77"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"parentDoc":null,"user":"566590c83889610d0008a253","category":{"_id":"56d96b03dd90610b00270849","__v":4,"pages":["56d96baddd90610b0027084d","56d9741554ee631300116633","56d97adc7222d50b0070151a","56d99d61dd90610b002708e1"],"project":"55faf11ba62ba1170021a9a7","version":"55faf11ba62ba1170021a9aa","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-03-04T11:01:23.735Z","from_sync":false,"order":11,"slug":"archive-files","title":"ARCHIVE FILES"},"__v":5,"project":"55faf11ba62ba1170021a9a7","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-03-04T11:04:13.272Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Storing large amounts of data in the cloud is a convenient way to have it available for computation. Instant availability is, however, not always our primary concern\n\n Sometimes we have to deal with \"cold\" data – files that are not required for processing and have a very low chance of being accessed over a longer time period, but must nonetheless remain available for compliance with local and federal laws, best practice guidelines and internal processes – such as input and output files belonging to completed analyses.\n\nData that will not be used for some time (typically over three months) can be moved into archival storage. Archived files are billed at a significantly reduced price compared to the data which is always available. This makes archival a good solution for infrequently accessed files.\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"The CGC currently offers Amazon Glacier as the archiving back-end. For up-to-date pricing information in the storage services that the CGC supports, please refer to the official pricing plans at [Amazon Glacier](https://aws.amazon.com/s3/pricing/).\"\n}\n[/block]\n## Cost Savings\n\nDepending on the storage service used, storing data in an archive typically costs around a third as much as storing data that is always available.\n\nAs with all other costs for user-uploaded data hosted on the Platform, the CGC passes the charges that we incur for archiving data directly to the customer without markup.\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"In July 2015, Amazon's S3 in the US East region charged $0.0275-0.03 per gigabyte of standard storage data per month. A gigabyte of data stored in Amazon's archiving facility, Glacier, in the same region was billed at $0.007 per month. Keeping data in Glacier rather than S3 would yield monthly savings of approximately 60%.\"\n}\n[/block]\nIn addition to data hosting charges, Amazon Glacier may charge additional archival, restoration or early deletion fees. If you incur these additional costs, then we will pass them on to you without markup.\n\nHowever, if archival storage is accessed infrequently over a number of months, these charges should not be expected to affect the projected cost savings significantly.\n\n## Limitations of Archiving\n\nMoving data to and from archival storage is not instantaneous. Depending on the type of archival storage used, it can take from several hours, up to a day or more to archive or restore large files.\n\nWhen archived, files can not be used as inputs to the tasks, downloaded, visualized in the Genome Browser nor can their content be obtained in any way. Archived files must first be restored.","excerpt":"","slug":"file-archiving-overview","type":"basic","title":"File archiving overview"}

File archiving overview


Storing large amounts of data in the cloud is a convenient way to have it available for computation. Instant availability is, however, not always our primary concern Sometimes we have to deal with "cold" data – files that are not required for processing and have a very low chance of being accessed over a longer time period, but must nonetheless remain available for compliance with local and federal laws, best practice guidelines and internal processes – such as input and output files belonging to completed analyses. Data that will not be used for some time (typically over three months) can be moved into archival storage. Archived files are billed at a significantly reduced price compared to the data which is always available. This makes archival a good solution for infrequently accessed files. [block:callout] { "type": "info", "body": "The CGC currently offers Amazon Glacier as the archiving back-end. For up-to-date pricing information in the storage services that the CGC supports, please refer to the official pricing plans at [Amazon Glacier](https://aws.amazon.com/s3/pricing/)." } [/block] ## Cost Savings Depending on the storage service used, storing data in an archive typically costs around a third as much as storing data that is always available. As with all other costs for user-uploaded data hosted on the Platform, the CGC passes the charges that we incur for archiving data directly to the customer without markup. [block:callout] { "type": "info", "body": "In July 2015, Amazon's S3 in the US East region charged $0.0275-0.03 per gigabyte of standard storage data per month. A gigabyte of data stored in Amazon's archiving facility, Glacier, in the same region was billed at $0.007 per month. Keeping data in Glacier rather than S3 would yield monthly savings of approximately 60%." } [/block] In addition to data hosting charges, Amazon Glacier may charge additional archival, restoration or early deletion fees. If you incur these additional costs, then we will pass them on to you without markup. However, if archival storage is accessed infrequently over a number of months, these charges should not be expected to affect the projected cost savings significantly. ## Limitations of Archiving Moving data to and from archival storage is not instantaneous. Depending on the type of archival storage used, it can take from several hours, up to a day or more to archive or restore large files. When archived, files can not be used as inputs to the tasks, downloaded, visualized in the Genome Browser nor can their content be obtained in any way. Archived files must first be restored.