<?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"
	>
<channel>
	<title>Comments on: Hitachi admits storage virtualization might not be for everyone</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/storage-soup/hitachi-admits-storage-virtualization-might-not-be-for-everyone/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/storage-soup/hitachi-admits-storage-virtualization-might-not-be-for-everyone/</link>
	<description>A SearchStorage.com blog.</description>
	<pubDate>Thu, 26 Nov 2009 16:03:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Loren Eslinger</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/hitachi-admits-storage-virtualization-might-not-be-for-everyone/#comment-6758</link>
		<dc:creator>Loren Eslinger</dc:creator>
		<pubDate>Wed, 25 Jul 2007 14:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2007/07/16/hitachi-admits-storage-virtualization-might-not-be-for-everyone/#comment-6758</guid>
		<description>While I find David comments accurate and fair (and far beyond the scope of what most companies will do for TCO), i am left wondering about some of the details of how and why this company is virutualizing 18TB of data?  

Comments from David like "an existing HP XP storage array" lead me to believe this is a single monolithic storage array with 18TB on it.  So why virutualize?  No real explaination is given other than projected growth patterns and this is want the company wants to do.  I currently use Virtualization so i am well versed in the pros of proactively moving to a virtualization strategy...but there is a lot of detail missing from David's blog that raises too many questions.

My first question would be why would a company even consider keeping around storage that is this old as there "Top Tier Storage"?  David's blog gives no indication that the company has any plans to change its current monolithic strategy on this storage array...quite the oposite.  David implies that this company wishs to continues to use this storage array for another 4 years front ended with the virtualization storage array (from david's blog: Total purchase cost for the virtualization solutions was, as you can guess, less than a monolithic, but the 4-year TCO...) and at the same level of service.  Why not just buy a new storage array and make it primary and move the old storage array to a low end need that doesn't require the support and maintenece costs?

You could question the need for virtualization all together.  If the company stays with the single storage array approach newer storage arrays offer many of the same features as virtualization...only limited to the single storage array.

My last observation is companies should realize there is a "cost" to keeping around older technologies and this article just demonstrates what most people in the industray already know.  Virtualization is a great way tool in the storage world but when put in place by bad philosophies and poorly thought out plans this is what happens.

It seems this company has not properly thought out their approach and how it relates to their business and costs before deciding on a virtualization strategy.</description>
		<content:encoded><![CDATA[<p>While I find David comments accurate and fair (and far beyond the scope of what most companies will do for TCO), i am left wondering about some of the details of how and why this company is virutualizing 18TB of data?  </p>
<p>Comments from David like &#8220;an existing HP XP storage array&#8221; lead me to believe this is a single monolithic storage array with 18TB on it.  So why virutualize?  No real explaination is given other than projected growth patterns and this is want the company wants to do.  I currently use Virtualization so i am well versed in the pros of proactively moving to a virtualization strategy&#8230;but there is a lot of detail missing from David&#8217;s blog that raises too many questions.</p>
<p>My first question would be why would a company even consider keeping around storage that is this old as there &#8220;Top Tier Storage&#8221;?  David&#8217;s blog gives no indication that the company has any plans to change its current monolithic strategy on this storage array&#8230;quite the oposite.  David implies that this company wishs to continues to use this storage array for another 4 years front ended with the virtualization storage array (from david&#8217;s blog: Total purchase cost for the virtualization solutions was, as you can guess, less than a monolithic, but the 4-year TCO&#8230;) and at the same level of service.  Why not just buy a new storage array and make it primary and move the old storage array to a low end need that doesn&#8217;t require the support and maintenece costs?</p>
<p>You could question the need for virtualization all together.  If the company stays with the single storage array approach newer storage arrays offer many of the same features as virtualization&#8230;only limited to the single storage array.</p>
<p>My last observation is companies should realize there is a &#8220;cost&#8221; to keeping around older technologies and this article just demonstrates what most people in the industray already know.  Virtualization is a great way tool in the storage world but when put in place by bad philosophies and poorly thought out plans this is what happens.</p>
<p>It seems this company has not properly thought out their approach and how it relates to their business and costs before deciding on a virtualization strategy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the storage anarchist</title>
		<link>http://itknowledgeexchange.techtarget.com/storage-soup/hitachi-admits-storage-virtualization-might-not-be-for-everyone/#comment-6757</link>
		<dc:creator>the storage anarchist</dc:creator>
		<pubDate>Mon, 16 Jul 2007 23:58:27 +0000</pubDate>
		<guid isPermaLink="false">http://storage.blogs.techtarget.com/2007/07/16/hitachi-admits-storage-virtualization-might-not-be-for-everyone/#comment-6757</guid>
		<description>Seems David's blog-site has lost all of his articles from June '07. In case you're interesting (as I was) you can find a cached copy of the referenced entry here: 

http://216.239.51.104/search?q=cache:Qei5L3FA8SgJ:blogs.hds.com/david/2007/06/virtualization_cross-over_points.html&#38;hl=en&#38;ct=clnk&#38;cd=1&#38;gl=us 

Hopefully David will get this repaired soon...

tsa</description>
		<content:encoded><![CDATA[<p>Seems David&#8217;s blog-site has lost all of his articles from June &#8216;07. In case you&#8217;re interesting (as I was) you can find a cached copy of the referenced entry here:<br />
&nbsp;&lt;a href="http://216.239.51.104/search?q=cache:Qei5L3FA8SgJ:blogs.hds.com/david/2007/06/virtualization_cross-over_points.html&amp;hl=en&amp;ct=clnk&amp;cd=1&amp;gl=us" title="http://216.239.51.104/search?q=cache:Qei5L3FA8SgJ:blogs.hds.com/david/2007/06/virtualization_cross-over_points.html&amp;hl=en&amp;ct=clnk&amp;cd=1&amp;gl=us" target="_blank"&gt;http://216.239.51.104/search?q=cache:Qei&#8230;&lt;/a&gt; </p>
<p>Hopefully David will get this repaired soon&#8230;</p>
<p>tsa</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->