<?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: Why policy is the future of storage, part 2</title>
	<atom:link href="http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/</link>
	<description>a Blog dedicated to storage and technology</description>
	<lastBuildDate>Wed, 03 Mar 2010 13:51:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Policy! Policy!! Policy!!! &#124; StorageNerve</title>
		<link>http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/comment-page-1/#comment-362</link>
		<dc:creator>Policy! Policy!! Policy!!! &#124; StorageNerve</dc:creator>
		<pubDate>Tue, 20 Oct 2009 05:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://flickerdown.com/?p=683#comment-362</guid>
		<description>[...] http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/" rel="nofollow">http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sfoskett</title>
		<link>http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/comment-page-1/#comment-429</link>
		<dc:creator>sfoskett</dc:creator>
		<pubDate>Mon, 05 Oct 2009 20:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://flickerdown.com/?p=683#comment-429</guid>
		<description>Dave, I totally agree that policy is the future of not just storage but IT in general. The issue is that we storage folks sometimes can&#039;t see the flowers for the weeds - we are so interested in LUNs and replication that we forget that these are the lowest-level, least-interesting policy questions possible. Business applications want business policy, not IT infrastructure issues. They want real operational data retention, not backup or replication. They want litigation readiness, not just data protection or indexing. They want collaboration, not just movement of data. Until storage can be programmed and integrated with applications, we&#039;re still in the weeds.</description>
		<content:encoded><![CDATA[<p>Dave, I totally agree that policy is the future of not just storage but IT in general. The issue is that we storage folks sometimes can&#39;t see the flowers for the weeds &#8211; we are so interested in LUNs and replication that we forget that these are the lowest-level, least-interesting policy questions possible. Business applications want business policy, not IT infrastructure issues. They want real operational data retention, not backup or replication. They want litigation readiness, not just data protection or indexing. They want collaboration, not just movement of data. Until storage can be programmed and integrated with applications, we&#39;re still in the weeds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sfoskett</title>
		<link>http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/comment-page-1/#comment-358</link>
		<dc:creator>sfoskett</dc:creator>
		<pubDate>Mon, 05 Oct 2009 15:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://flickerdown.com/?p=683#comment-358</guid>
		<description>Dave, I totally agree that policy is the future of not just storage but IT in general. The issue is that we storage folks sometimes can&#039;t see the flowers for the weeds - we are so interested in LUNs and replication that we forget that these are the lowest-level, least-interesting policy questions possible. Business applications want business policy, not IT infrastructure issues. They want real operational data retention, not backup or replication. They want litigation readiness, not just data protection or indexing. They want collaboration, not just movement of data. Until storage can be programmed and integrated with applications, we&#039;re still in the weeds.</description>
		<content:encoded><![CDATA[<p>Dave, I totally agree that policy is the future of not just storage but IT in general. The issue is that we storage folks sometimes can&#39;t see the flowers for the weeds &#8211; we are so interested in LUNs and replication that we forget that these are the lowest-level, least-interesting policy questions possible. Business applications want business policy, not IT infrastructure issues. They want real operational data retention, not backup or replication. They want litigation readiness, not just data protection or indexing. They want collaboration, not just movement of data. Until storage can be programmed and integrated with applications, we&#39;re still in the weeds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Why policy is the future of storage, part 2 — Dave Graham's Weblog -- Topsy.com</title>
		<link>http://flickerdown.com/2009/10/why-policy-is-the-future-of-storage-part-2/comment-page-1/#comment-357</link>
		<dc:creator>Tweets that mention Why policy is the future of storage, part 2 — Dave Graham's Weblog -- Topsy.com</dc:creator>
		<pubDate>Mon, 05 Oct 2009 13:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://flickerdown.com/?p=683#comment-357</guid>
		<description>[...] This post was mentioned on Twitter by Collin MacMillan and Dennis Smith. Dennis Smith said: RT @davegraham: Blog Post: Why policy is the future of storage, part 2 http://bit.ly/37s88 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Collin MacMillan and Dennis Smith. Dennis Smith said: RT @davegraham: Blog Post: Why policy is the future of storage, part 2 <a href="http://bit.ly/37s88" rel="nofollow">http://bit.ly/37s88</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
