<?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: HP and Hitachi</title>
	<atom:link href="http://blog.nigelpoulton.com/hp-and-hitachi/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nigelpoulton.com/hp-and-hitachi/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
	<description>with nigel poulton</description>
	<lastBuildDate>Wed, 28 Jul 2010 04:41:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Logicalis HP Storage</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-750</link>
		<dc:creator>Logicalis HP Storage</dc:creator>
		<pubDate>Wed, 21 Apr 2010 19:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-750</guid>
		<description>HP has been much better in terms of storage than Hitachi.</description>
		<content:encoded><![CDATA[<p>HP has been much better in terms of storage than Hitachi.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James R Wilson</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-703</link>
		<dc:creator>James R Wilson</dc:creator>
		<pubDate>Fri, 22 Jan 2010 01:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-703</guid>
		<description>Just to be clear, I am James R. Wilson, the HP XP product manager quoted above. I am not the JRW who has made the other informative and informed comments. That is someone else. When I comment here, I will use my full name and position at HP.
Just a couple of points, while I am here. NonStop is still a very significant business for HP. NonStop does indeed manage a huge share of the ATM market, or cash points, as they are called in some countries. XP support for NonStop is unique to XP.
MetroCluster support is one reason why Hitachi does sell the XP version of the array in Japan. Hitachi is a very significant reseller of HP equipment in Japan. Using the XP version lets them sell a complete HP integrated disaster recovery solution as an official HP reseller.
Thanks for the interest in XP Disk Arrays.
James R. Wilson, XP Product Manager</description>
		<content:encoded><![CDATA[<p>Just to be clear, I am James R. Wilson, the HP XP product manager quoted above. I am not the JRW who has made the other informative and informed comments. That is someone else. When I comment here, I will use my full name and position at HP.<br />
Just a couple of points, while I am here. NonStop is still a very significant business for HP. NonStop does indeed manage a huge share of the ATM market, or cash points, as they are called in some countries. XP support for NonStop is unique to XP.<br />
MetroCluster support is one reason why Hitachi does sell the XP version of the array in Japan. Hitachi is a very significant reseller of HP equipment in Japan. Using the XP version lets them sell a complete HP integrated disaster recovery solution as an official HP reseller.<br />
Thanks for the interest in XP Disk Arrays.<br />
James R. Wilson, XP Product Manager</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Ruby</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-690</link>
		<dc:creator>Steven Ruby</dc:creator>
		<pubDate>Sun, 17 Jan 2010 21:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-690</guid>
		<description>
	&gt;It&#8217;s the same issue with USP to 9990
	&gt;USP to 9990 replication works like charm, no limitations.
	Yes it does.
	&#160;
</description>
		<content:encoded><![CDATA[<p>&gt;It&rsquo;s the same issue with USP to 9990<br />
	&gt;USP to 9990 replication works like charm, no limitations.<br />
	Yes it does.<br />
	&nbsp;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Poulton</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-649</link>
		<dc:creator>Nigel Poulton</dc:creator>
		<pubDate>Fri, 11 Dec 2009 23:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-649</guid>
		<description>Hi Calvin,

Thanks for dropping by and clarifying that . I knew it was something along those lines.

Nigel</description>
		<content:encoded><![CDATA[<p>Hi Calvin,</p>
<p>Thanks for dropping by and clarifying that . I knew it was something along those lines.</p>
<p>Nigel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Calvin Zito</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-647</link>
		<dc:creator>Calvin Zito</dc:creator>
		<pubDate>Fri, 11 Dec 2009 22:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-647</guid>
		<description>The story behind the original XP256 name is interesting.&#160; At the time, HP was using SureStore as a entry level storage brand and we decided to use SureStore E as our enterprise storage brand.&#160; The original name of the XP was the HP SureStore E Disk Array MC256, not SureStore E MC256.&#160; But in some of the first articles when we announced it, they botched the name and you can imaging that a few people in Hopkinton didn&#039;t like that.
&lt;a href=&quot;http://twitter.com/HPstorageGuy&quot; rel=&quot;nofollow&quot;&gt;http://twitter.com/HPstorageGuy&lt;/a&gt; and &lt;a href=&quot;http://www.hp.com/storage/blog&quot; rel=&quot;nofollow&quot;&gt;www.hp.com/storage/blog&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>The story behind the original XP256 name is interesting.&nbsp; At the time, HP was using SureStore as a entry level storage brand and we decided to use SureStore E as our enterprise storage brand.&nbsp; The original name of the XP was the HP SureStore E Disk Array MC256, not SureStore E MC256.&nbsp; But in some of the first articles when we announced it, they botched the name and you can imaging that a few people in Hopkinton didn&#39;t like that.<br />
<a href="http://twitter.com/HPstorageGuy" rel="nofollow">http://twitter.com/HPstorageGuy</a> and <a href="http://www.hp.com/storage/blog" rel="nofollow">http://www.hp.com/storage/blog</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IvanE</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-625</link>
		<dc:creator>IvanE</dc:creator>
		<pubDate>Wed, 09 Dec 2009 05:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-625</guid>
		<description>&gt;It’s the same issue with USP to 9990 

USP to 9990 replication works like charm, no limitations.</description>
		<content:encoded><![CDATA[<p>&gt;It’s the same issue with USP to 9990 </p>
<p>USP to 9990 replication works like charm, no limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Ruby</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-623</link>
		<dc:creator>Steven Ruby</dc:creator>
		<pubDate>Tue, 08 Dec 2009 22:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-623</guid>
		<description>USP to XP replication is all a sales thing. It&#039;s the same issue with USP to 9990 replication. The only diff is HP will still be in business next year, I cant say the same for Sun.</description>
		<content:encoded><![CDATA[<p>USP to XP replication is all a sales thing. It&#8217;s the same issue with USP to 9990 replication. The only diff is HP will still be in business next year, I cant say the same for Sun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IvanE</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-622</link>
		<dc:creator>IvanE</dc:creator>
		<pubDate>Tue, 08 Dec 2009 19:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-622</guid>
		<description>&gt;Hitachi Storage Cluster/SplitSecond are professional service engagments. While HP&#039;s Cluster Extensions is a product that continues to be refined it is ahead of HSC

I&#039;ve never seen HP Cluster Extensions sold without implementation service, thus don&#039;t see much difference.

Anyway, this doesn&#039;t change the overall idea - XP and USP V are the same, the difference is in the vendor and added value you expect from him. And obviously anyone in this business can bring dozens of examples where one vendor&#039;s value was higher than others and vice versa.

&gt;My take is that it is still using the cache bus that general I/Os are using

Correct.</description>
		<content:encoded><![CDATA[<p>&gt;Hitachi Storage Cluster/SplitSecond are professional service engagments. While HP&#8217;s Cluster Extensions is a product that continues to be refined it is ahead of HSC</p>
<p>I&#8217;ve never seen HP Cluster Extensions sold without implementation service, thus don&#8217;t see much difference.</p>
<p>Anyway, this doesn&#8217;t change the overall idea &#8211; XP and USP V are the same, the difference is in the vendor and added value you expect from him. And obviously anyone in this business can bring dozens of examples where one vendor&#8217;s value was higher than others and vice versa.</p>
<p>&gt;My take is that it is still using the cache bus that general I/Os are using</p>
<p>Correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JRW</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-621</link>
		<dc:creator>JRW</dc:creator>
		<pubDate>Tue, 08 Dec 2009 19:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-621</guid>
		<description>Hi IvanE, 
Most of the CLIs are the same, just with different names, making skills quite portable, but to the best of my knowledge XPWatch hasn&#039;t got non-HP versions - it would be interesting to hear if this has changed. Hitachi Storage Cluster/SplitSecond are professional service engagments. While HP&#039;s Cluster Extensions is a product that continues to be refined it is ahead of HSC. MetroCluster support is different matter from CLX, it would work very well on USP-V if HP wanted to support it, but that&#039;s for people to ask HP. Certainly Non-Stop is a fairly stable market ;-) (I&#039;m told it still runs most the cash points etc..)
Costs are a bit like cross vendor replication.&#160; I&#039;ve heard both say they have a cost advantage, and a cost disadvantage, depending who is speaking. I suspect neither has the edge here, and as on replication a definitive answer is elusive.
Interesting what you say on V-Max. My take is that it is still using the cache bus that general I/Os are using, so the more clever things you try to do with metadata the less bandwidth is available for data. 
Cheers - JRW</description>
		<content:encoded><![CDATA[<p>Hi IvanE,<br />
Most of the CLIs are the same, just with different names, making skills quite portable, but to the best of my knowledge XPWatch hasn&#39;t got non-HP versions &#8211; it would be interesting to hear if this has changed. Hitachi Storage Cluster/SplitSecond are professional service engagments. While HP&#39;s Cluster Extensions is a product that continues to be refined it is ahead of HSC. MetroCluster support is different matter from CLX, it would work very well on USP-V if HP wanted to support it, but that&#39;s for people to ask HP. Certainly Non-Stop is a fairly stable market <img src='http://blog.nigelpoulton.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  (I&#39;m told it still runs most the cash points etc..)<br />
Costs are a bit like cross vendor replication.&nbsp; I&#39;ve heard both say they have a cost advantage, and a cost disadvantage, depending who is speaking. I suspect neither has the edge here, and as on replication a definitive answer is elusive.<br />
Interesting what you say on V-Max. My take is that it is still using the cache bus that general I/Os are using, so the more clever things you try to do with metadata the less bandwidth is available for data.<br />
Cheers &#8211; JRW</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IvanE</title>
		<link>http://blog.nigelpoulton.com/hp-and-hitachi/comment-page-1/#comment-620</link>
		<dc:creator>IvanE</dc:creator>
		<pubDate>Tue, 08 Dec 2009 17:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=613#comment-620</guid>
		<description>&gt;XP Tools are CLI utilities that you only get with the XP
Oh? Rebranded SNM and SNM CLI you mean?

&gt;HP have superior cluster integration
Oh, c&#039;mon! You mean Metrocluster? The one that worked perfectly fine with USP after changing single line in script until HP compiled it into binary? And BTW, this didn&#039;t leave HDS without solution - Hitachi Storage Cluster is available for most OSes out there. The only difference is support for NonStop line (cough, cough, how many of them are still used?).
&gt;As for not replicating to each other both HDS and HP wanted this from the beginning 
Well, I heard slightly different but it&#039;s impossible to get definite answer here.

&gt;Both arrays are great and customers should go with the supplier that suits them.
Totaly agree here :)

&gt;Still metadata in general cache
It&#039;s not anymore. It same physical memory but the area is dedicated for metadata, can&#039;t be mixed with data cache. 80 gigs in fully configured V-max</description>
		<content:encoded><![CDATA[<p>&gt;XP Tools are CLI utilities that you only get with the XP<br />
Oh? Rebranded SNM and SNM CLI you mean?</p>
<p>&gt;HP have superior cluster integration<br />
Oh, c&#8217;mon! You mean Metrocluster? The one that worked perfectly fine with USP after changing single line in script until HP compiled it into binary? And BTW, this didn&#8217;t leave HDS without solution &#8211; Hitachi Storage Cluster is available for most OSes out there. The only difference is support for NonStop line (cough, cough, how many of them are still used?).<br />
&gt;As for not replicating to each other both HDS and HP wanted this from the beginning<br />
Well, I heard slightly different but it&#8217;s impossible to get definite answer here.</p>
<p>&gt;Both arrays are great and customers should go with the supplier that suits them.<br />
Totaly agree here <img src='http://blog.nigelpoulton.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>&gt;Still metadata in general cache<br />
It&#8217;s not anymore. It same physical memory but the area is dedicated for metadata, can&#8217;t be mixed with data cache. 80 gigs in fully configured V-max</p>
]]></content:encoded>
	</item>
</channel>
</rss>
