<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Amazon Delivers Glacier for Archival Storage</title>
	<atom:link href="http://diversity.net.nz/amazon-delivers-glacier-for-archival-storage/2012/08/22/feed/" rel="self" type="application/rss+xml" />
	<link>http://diversity.net.nz/amazon-delivers-glacier-for-archival-storage/2012/08/22/</link>
	<description>Thoughts on the Future of Business and User-Centered Technology</description>
	<lastBuildDate>Fri, 17 May 2013 23:52:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Chris Haddad</title>
		<link>http://diversity.net.nz/amazon-delivers-glacier-for-archival-storage/2012/08/22/comment-page-1/#comment-130051</link>
		<dc:creator>Chris Haddad</dc:creator>
		<pubDate>Wed, 22 Aug 2012 18:45:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.diversity.net.nz/?p=9306#comment-130051</guid>
		<description><![CDATA[The cost calculation will provide complex. If the data is not already in an Amazon zone, network I/O metering charges apply. &quot;Data transferred between Amazon EC2 and Amazon Glacier across all other Regions will be charged at Internet Data Transfer rates on both sides of the transfer.&quot;

What eDiscovery options are available on top of Glacier?  Enterprise organizations often require eDiscovery. Or, must all information conforming a specific time period or meta-data be first transferred out of Glacier? 

Seems like Glacier provides little meta-data, or even timestamps.   The client is responsible for maintaining archive meta-data and linking the meta-data to retrieval systems: &quot;Amazon Glacier does not support any additional metadata for the archives. The archive ID is an opaque sequence of characters from which you cannot infer any meaning about the archive. So you might maintain metadata about the archives on the client-side. &quot;]]></description>
		<content:encoded><![CDATA[<p>The cost calculation will provide complex. If the data is not already in an Amazon zone, network I/O metering charges apply. &#8220;Data transferred between Amazon EC2 and Amazon Glacier across all other Regions will be charged at Internet Data Transfer rates on both sides of the transfer.&#8221;</p>
<p>What eDiscovery options are available on top of Glacier?  Enterprise organizations often require eDiscovery. Or, must all information conforming a specific time period or meta-data be first transferred out of Glacier? </p>
<p>Seems like Glacier provides little meta-data, or even timestamps.   The client is responsible for maintaining archive meta-data and linking the meta-data to retrieval systems: &#8220;Amazon Glacier does not support any additional metadata for the archives. The archive ID is an opaque sequence of characters from which you cannot infer any meaning about the archive. So you might maintain metadata about the archives on the client-side. &#8220;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
