<?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: What I Want From A Storage Virtualization Engine</title>
	<atom:link href="http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/feed/" rel="self" type="application/rss+xml" />
	<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/</link>
	<description>im in ur data centrz patchin ur serverz</description>
	<pubDate>Wed, 07 Jan 2009 00:20:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tricher au poker en ligne</title>
		<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/comment-page-1/#comment-74218</link>
		<dc:creator>tricher au poker en ligne</dc:creator>
		<pubDate>Wed, 04 Jun 2008 18:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/#comment-74218</guid>
		<description>&lt;strong&gt;tricher au poker en ligne...&lt;/strong&gt;

Ainsi casinos web video poker online 24 ringtones show tv poker regeln straight baccarat online spiele...</description>
		<content:encoded><![CDATA[<p><strong>tricher au poker en ligne&#8230;</strong></p>
<p>Ainsi casinos web video poker online 24 ringtones show tv poker regeln straight baccarat online spiele&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Messaging&#8230;.. Technology&#8230;&#8230; Life&#8230;.. &#187; Virtualization Wish List</title>
		<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/comment-page-1/#comment-5449</link>
		<dc:creator>Messaging&#8230;.. Technology&#8230;&#8230; Life&#8230;.. &#187; Virtualization Wish List</dc:creator>
		<pubDate>Mon, 14 Aug 2006 12:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/#comment-5449</guid>
		<description>[...] The Lone Sysadmin is not alone in his Storage Virtualization wish list. I agree with some of the things he says and Brian from Steriod.com points out items 1 and 2 are a mix between virtualization and site resiliency. EMC does SRDF/CE for site resiliency, HP, and HDS have their solutions as well. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Lone Sysadmin is not alone in his Storage Virtualization wish list. I agree with some of the things he says and Brian from Steriod.com points out items 1 and 2 are a mix between virtualization and site resiliency. EMC does SRDF/CE for site resiliency, HP, and HDS have their solutions as well. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/comment-page-1/#comment-4429</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 26 Jul 2006 05:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/#comment-4429</guid>
		<description>Great wishlist.  They're pretty consistent with what we've been told by our customers and prospects.  I'm pleased to say that most of these (not sure about the RAID-1 request) are part of the design goals for future versions of our storage virtualization.  As noted, however, these are not trivial.  And, lots of options on how to implement them.  

We've found that while there's a lot of interest in automation the overwhelming majority of our customers don't want our storage systems to implement changes on their own.  Part of the issue is trusting our systems to make good decisions, but much of it is that a human consider other business factors.  What most customers want is for our systems to make intelligent recommendations and then let a human make a go/no-go decision.

Rick, Product Marketing, Hitachi Data Systems

Note that the comments above are personal interpretation and do not necessarily reflect corporate position.</description>
		<content:encoded><![CDATA[<p>Great wishlist.  They&#8217;re pretty consistent with what we&#8217;ve been told by our customers and prospects.  I&#8217;m pleased to say that most of these (not sure about the RAID-1 request) are part of the design goals for future versions of our storage virtualization.  As noted, however, these are not trivial.  And, lots of options on how to implement them.  </p>
<p>We&#8217;ve found that while there&#8217;s a lot of interest in automation the overwhelming majority of our customers don&#8217;t want our storage systems to implement changes on their own.  Part of the issue is trusting our systems to make good decisions, but much of it is that a human consider other business factors.  What most customers want is for our systems to make intelligent recommendations and then let a human make a go/no-go decision.</p>
<p>Rick, Product Marketing, Hitachi Data Systems</p>
<p>Note that the comments above are personal interpretation and do not necessarily reflect corporate position.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Lone Sysadmin &#187; Musings on What I Want From Storage Virtualization</title>
		<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/comment-page-1/#comment-4371</link>
		<dc:creator>The Lone Sysadmin &#187; Musings on What I Want From Storage Virtualization</dc:creator>
		<pubDate>Mon, 24 Jul 2006 03:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/#comment-4371</guid>
		<description>[...] Brian over at stereoroid.com commented on my last post about what I want from a storage virtualization engine. Brian, I hope you don&#8217;t mind but I&#8217;d like to answer outside of the comments section. Your comments were not counterpoint, they were more in the realm of adding clarity, something which my other post may have lacked. [...]</description>
		<content:encoded><![CDATA[<p>[...] Brian over at stereoroid.com commented on my last post about what I want from a storage virtualization engine. Brian, I hope you don&#8217;t mind but I&#8217;d like to answer outside of the comments section. Your comments were not counterpoint, they were more in the realm of adding clarity, something which my other post may have lacked. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian t</title>
		<link>http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/comment-page-1/#comment-4352</link>
		<dc:creator>brian t</dc:creator>
		<pubDate>Sun, 23 Jul 2006 18:43:26 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/23/what-i-want-from-a-storage-virtualization-engine/#comment-4352</guid>
		<description>I've been wondering about the possibility of transparent failover for a while now, but it's not as simple as it seems. The array system I'm most familiar with is one you don't mention, the HP Enterprise Virtual Array (EVA). All the critical components are duplicated e.g. it has 2 storage controllers with transparent failover, dual back-end loops, and dual SANs (switches, HBAs etc.) is the norm. No SPOF unless you set up RAID-0 volumes. You have data replication to another array if you want. 

However, you're talking about failover between complete arrays, a.k.a. "site failover", since real disaster recovery means having arrays on different physical sites. That's a bit more serious: if there is a real disaster, you've lost the servers AND the arrays at one site, so you hope to fail all that over at once. Trying to make that fully transparent is a tall order. 

The kind of thing you're talking about is what HP call "Cluster Extensions" (CLX), which can automate "site failover" of arrays and server clusters at the same time. Needs a lot of planning and testing, but the result is transparent failover at the "share" level (where clients attach to clusters).</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been wondering about the possibility of transparent failover for a while now, but it&#8217;s not as simple as it seems. The array system I&#8217;m most familiar with is one you don&#8217;t mention, the HP Enterprise Virtual Array (EVA). All the critical components are duplicated e.g. it has 2 storage controllers with transparent failover, dual back-end loops, and dual SANs (switches, HBAs etc.) is the norm. No SPOF unless you set up RAID-0 volumes. You have data replication to another array if you want. </p>
<p>However, you&#8217;re talking about failover between complete arrays, a.k.a. &#8220;site failover&#8221;, since real disaster recovery means having arrays on different physical sites. That&#8217;s a bit more serious: if there is a real disaster, you&#8217;ve lost the servers AND the arrays at one site, so you hope to fail all that over at once. Trying to make that fully transparent is a tall order. </p>
<p>The kind of thing you&#8217;re talking about is what HP call &#8220;Cluster Extensions&#8221; (CLX), which can automate &#8220;site failover&#8221; of arrays and server clusters at the same time. Needs a lot of planning and testing, but the result is transparent failover at the &#8220;share&#8221; level (where clients attach to clusters).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
