<?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: Enterprise Computing: USP-V &#8211; So Long And Thanks For All The Fish</title>
	<atom:link href="http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/feed/" rel="self" type="application/rss+xml" />
	<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/</link>
	<description>Storage, Virtualisation &#38; Cloud</description>
	<lastBuildDate>Sat, 11 Feb 2012 00:09:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Hitachi VSP SPC-1 Results posted &#171; TechOpsGuys.com</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-2494</link>
		<dc:creator>Hitachi VSP SPC-1 Results posted &#171; TechOpsGuys.com</dc:creator>
		<pubDate>Sat, 05 Nov 2011 17:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-2494</guid>
		<description>[...] The other interesting aspect of the VSP is it&#8217;s dual chassis design(each chassis in a separate rack), which, the white paper says is not a cluster, unlike a VMAX or a 3PAR system. I would assume this is in response to earlier criticisms of the USP-V design in which the virtualization layer was not redundant(when I learned that I was honestly pretty shocked) &#8211; Hitachi later rectified the situation on the USP-V by adding some magic sauce that allowed you to link a pair of them together. [...]</description>
		<content:encoded><![CDATA[<p>[...] The other interesting aspect of the VSP is it&#8217;s dual chassis design(each chassis in a separate rack), which, the white paper says is not a cluster, unlike a VMAX or a 3PAR system. I would assume this is in response to earlier criticisms of the USP-V design in which the virtualization layer was not redundant(when I learned that I was honestly pretty shocked) &#8211; Hitachi later rectified the situation on the USP-V by adding some magic sauce that allowed you to link a pair of them together. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: storage thanks</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-874</link>
		<dc:creator>storage thanks</dc:creator>
		<pubDate>Sat, 05 Dec 2009 08:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-874</guid>
		<description>1.how to how to deal with the fact
  that the USP is SPOF (Single Point of Failure)?
2.What causes a SPOF USP (Single Point of Failure)?
3.What primary function clustering USP ?
4.What are the deficiencies and excess clustering USP ?
5.whether to use clustering USP, should require other
  hardware that can be used clustering USP?</description>
		<content:encoded><![CDATA[<p>1.how to how to deal with the fact<br />
  that the USP is SPOF (Single Point of Failure)?<br />
2.What causes a SPOF USP (Single Point of Failure)?<br />
3.What primary function clustering USP ?<br />
4.What are the deficiencies and excess clustering USP ?<br />
5.whether to use clustering USP, should require other<br />
  hardware that can be used clustering USP?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Evans</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-872</link>
		<dc:creator>Chris Evans</dc:creator>
		<pubDate>Mon, 26 Oct 2009 20:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-872</guid>
		<description>Mpho

I&#039;m not sure what you&#039;re trying to achieve here.  You&#039;ve lots of different variables but I don&#039;t know how they combine.  What figure are you trying to calculate?

Chris</description>
		<content:encoded><![CDATA[<p>Mpho</p>
<p>I&#8217;m not sure what you&#8217;re trying to achieve here.  You&#8217;ve lots of different variables but I don&#8217;t know how they combine.  What figure are you trying to calculate?</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mpho</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-873</link>
		<dc:creator>Mpho</dc:creator>
		<pubDate>Mon, 26 Oct 2009 08:39:46 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-873</guid>
		<description>How do I calculate capacity of storage needed if I am given the following.

Numbero accounts = 5000-100000
Number of ATM&#039;s  = 256
Number of books store = 500
Number of call centres = 9
Estimated transaction rates = 500/sec

I what know if I will need AMS or USP</description>
		<content:encoded><![CDATA[<p>How do I calculate capacity of storage needed if I am given the following.</p>
<p>Numbero accounts = 5000-100000<br />
Number of ATM&#8217;s  = 256<br />
Number of books store = 500<br />
Number of call centres = 9<br />
Estimated transaction rates = 500/sec</p>
<p>I what know if I will need AMS or USP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Computing: New HDS AMS – Do We Need Enterprise Storage? &#8211; Gestalt IT</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-871</link>
		<dc:creator>Enterprise Computing: New HDS AMS – Do We Need Enterprise Storage? &#8211; Gestalt IT</dc:creator>
		<pubDate>Tue, 30 Jun 2009 18:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-871</guid>
		<description>[...] I touched on this subject not that long ago when I criticised the recent USP-V clustering announcement.  Looking at what the AMS offers today, it’s not that [...] </description>
		<content:encoded><![CDATA[<p>[...] I touched on this subject not that long ago when I criticised the recent USP-V clustering announcement.  Looking at what the AMS offers today, it’s not that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Computing: New HDS AMS &#8211; Do We Need Enterprise Storage? &#171; The Storage Architect</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-870</link>
		<dc:creator>Enterprise Computing: New HDS AMS &#8211; Do We Need Enterprise Storage? &#171; The Storage Architect</dc:creator>
		<pubDate>Tue, 30 Jun 2009 08:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-870</guid>
		<description>[...] Top Posts Enterprise Computing: Why Thin Provisioning Is Not The Holy Grail for UtilisationEnterprise Computing: VMware Announce vSphere 4Enterprise Computing: Barclays Bank Services Down Due to Storage Array ProblemsChanging Times - Looking For New WorkReview: Sun Storage 7000 Unified Storage System - Part IEnterprise Computing: Is DMX The Worst Array for Wastage?Review: Sun Storage 7000 Unified Storage System - Part IICloud Computing: Have You Got Your Atmos onLine Account?Cloud Computing: Emulex Enterprise Elastic Storage (E3S)Enterprise Computing: USP-V - So Long And Thanks For All The Fish [...] </description>
		<content:encoded><![CDATA[<p>[...] Top Posts Enterprise Computing: Why Thin Provisioning Is Not The Holy Grail for UtilisationEnterprise Computing: VMware Announce vSphere 4Enterprise Computing: Barclays Bank Services Down Due to Storage Array ProblemsChanging Times &#8211; Looking For New WorkReview: Sun Storage 7000 Unified Storage System &#8211; Part IEnterprise Computing: Is DMX The Worst Array for Wastage?Review: Sun Storage 7000 Unified Storage System &#8211; Part IICloud Computing: Have You Got Your Atmos onLine Account?Cloud Computing: Emulex Enterprise Elastic Storage (E3S)Enterprise Computing: USP-V &#8211; So Long And Thanks For All The Fish [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HDS High Availability Manager: How It Works &#8211; Gestalt IT</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-869</link>
		<dc:creator>HDS High Availability Manager: How It Works &#8211; Gestalt IT</dc:creator>
		<pubDate>Sat, 13 Jun 2009 12:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-869</guid>
		<description>[...] confusing others. Now that the dust has settled some, it has become clearer just what HAM is and how it works, and we come away more impressed. HDS has taken simple, proven technologies (path management, [...] </description>
		<content:encoded><![CDATA[<p>[...] confusing others. Now that the dust has settled some, it has become clearer just what HAM is and how it works, and we come away more impressed. HDS has taken simple, proven technologies (path management, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Taste Of HAM (Apologies To The Doctor) &#8211; Gestalt IT</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-868</link>
		<dc:creator>A Taste Of HAM (Apologies To The Doctor) &#8211; Gestalt IT</dc:creator>
		<pubDate>Sat, 13 Jun 2009 12:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-868</guid>
		<description>[...] My data has replication/Your brain must be on [...] </description>
		<content:encoded><![CDATA[<p>[...] My data has replication/Your brain must be on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HDS&#8217; HAM-Fisted Announcement Can&#8217;t Be All &#8211; Gestalt IT</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-867</link>
		<dc:creator>HDS&#8217; HAM-Fisted Announcement Can&#8217;t Be All &#8211; Gestalt IT</dc:creator>
		<pubDate>Sat, 13 Jun 2009 12:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-867</guid>
		<description>[...] Manager (we&#8217;re calling it HAM for now) really is. As noted by our own Chris Evans (USP-V – So Long And Thanks For All The Fish), HAM isn&#8217;t the next-generation USP-V with more-granular thin provisioning, automatic storage [...] </description>
		<content:encoded><![CDATA[<p>[...] Manager (we&#8217;re calling it HAM for now) really is. As noted by our own Chris Evans (USP-V – So Long And Thanks For All The Fish), HAM isn&#8217;t the next-generation USP-V with more-granular thin provisioning, automatic storage [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: soikki</title>
		<link>http://thestoragearchitect.com/2009/05/27/enterprise-computing-usp-v-so-long-and-thanks-for-all-the-fish/#comment-866</link>
		<dc:creator>soikki</dc:creator>
		<pubDate>Sat, 13 Jun 2009 11:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.com/?p=583#comment-866</guid>
		<description>First, please read EMC&#039;s document &quot;Best Practices for Nondisruptive Tiering via EMC® Symmetrix® Virtual LUN&quot;

Yes, the HW on V-Max looks promising. However, currently the features are missing: there&#039;s no possibility for real tiering, as you cannot migrate data even inside the box from &quot;normal&quot; luns to &quot;thin&quot; luns. And as I&#039;ve heard, you cannot do lun migrations on thin luns at all. This is seriously flawed and I&#039;m very surprised that there&#039;s no attention to this. And when migrating luns, the source is _always_ erased = you cannot use it for repurposing data.

Also, the only way to expand luns is by creating meta&#039;s and this kind of storage configuration is from the dark middle ages.

At some point I&#039;m sure that the V-Max will be usable, but currently there is too little to get excited about, when you are the person who has to really work with it. I&#039;m quite sure that the lacking features are due to the microcode inheritance, which brings too many restrictions originated from the 90&#039;s.

It is also too bad that HDS has a lot of nice features, but as you stated, the user interface is lacking and of bad design. I wonder when will we get the best of both worlds...

-Soikki

And BTW, Open replicator means that data is copied offline.</description>
		<content:encoded><![CDATA[<p>First, please read EMC&#8217;s document &#8220;Best Practices for Nondisruptive Tiering via EMC® Symmetrix® Virtual LUN&#8221;</p>
<p>Yes, the HW on V-Max looks promising. However, currently the features are missing: there&#8217;s no possibility for real tiering, as you cannot migrate data even inside the box from &#8220;normal&#8221; luns to &#8220;thin&#8221; luns. And as I&#8217;ve heard, you cannot do lun migrations on thin luns at all. This is seriously flawed and I&#8217;m very surprised that there&#8217;s no attention to this. And when migrating luns, the source is _always_ erased = you cannot use it for repurposing data.</p>
<p>Also, the only way to expand luns is by creating meta&#8217;s and this kind of storage configuration is from the dark middle ages.</p>
<p>At some point I&#8217;m sure that the V-Max will be usable, but currently there is too little to get excited about, when you are the person who has to really work with it. I&#8217;m quite sure that the lacking features are due to the microcode inheritance, which brings too many restrictions originated from the 90&#8242;s.</p>
<p>It is also too bad that HDS has a lot of nice features, but as you stated, the user interface is lacking and of bad design. I wonder when will we get the best of both worlds&#8230;</p>
<p>-Soikki</p>
<p>And BTW, Open replicator means that data is copied offline.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

