<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: The Truth About HP&#8217;s Tech Day</title>
	<atom:link href="http://blog.fosketts.net/2009/10/01/hp-tech-day/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/</link>
	<description>Understanding the accumulation of data</description>
	<lastBuildDate>Sat, 11 Feb 2012 20:58:00 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Tech Field Day Preview: HP &#124; Standalone Sysadmin</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-14380</link>
		<dc:creator>Tech Field Day Preview: HP &#124; Standalone Sysadmin</dc:creator>
		<pubDate>Wed, 31 Mar 2010 08:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-14380</guid>
		<description>[...] long time. It&#8217;s sort of fitting that I&#8217;m covering them first, because it grew from the HP Tech Day that they hosted in [...]</description>
		<content:encoded><![CDATA[<p>[...] long time. It&#8217;s sort of fitting that I&#8217;m covering them first, because it grew from the HP Tech Day that they hosted in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scostigan</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-14036</link>
		<dc:creator>scostigan</dc:creator>
		<pubDate>Mon, 12 Oct 2009 16:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-14036</guid>
		<description>Interesting that you say you just don&#039;t get SVSP&lt;br&gt;some things to consider, you a removing the binding of the host from the back end array, &lt;br&gt;thus allowing any to any data migration as you want to retire and bring in new storage technology without downtime. &lt;br&gt;A single management interface for all advanced storage features regardless of the capabilities of the underlying array. &lt;br&gt;I think you probably had enough time to examine the intuitive GUI of SVSP and understand that it is simple to manage from a small to an enterprise estate&lt;br&gt;this all without the need to keep changing tools to complete tasks.&lt;br&gt;Many customers have differing technologies from many vendors and this provides a solution for managing the sprawling estate.&lt;br&gt;Just keeping this inside the array has many limitations and is akin to keeping VM&#039;s confined to a single server in the server virtualisation space.&lt;br&gt;Also this is done at wire speed with no cache to synchronise in the network, thus enabling stretched SVSP domain across metro distances so no LUN resignaturing for VMWare when synchronously mirroing between 2 EVA&#039;s, add to this asynchronous mirroring to a third location and you have a complete business critical solution.&lt;br&gt;SVSP provides the ability to use different storage pools for the writable snapshot region, enabling the use of provisioning the right storage for the right task.&lt;br&gt;Especially usefull for test and dev environments or combined with mirroring to provide disk to disk backup and offsite presentation of the replicated disk without breaking the mirroring &lt;br&gt;this allows you to do regular testing of your DR without the need to break the mirrors or do a full resynch after the test - many customers don&#039;t test DR often enough because of this&lt;br&gt;along with the powerful scripting API you can provide a great deal of automation without the need to have a different tool for each array&lt;br&gt;let me know if you need more help getting it :-)&lt;br&gt;Regards Steve</description>
		<content:encoded><![CDATA[<p>Interesting that you say you just don&#39;t get SVSP<br />some things to consider, you a removing the binding of the host from the back end array, <br />thus allowing any to any data migration as you want to retire and bring in new storage technology without downtime. <br />A single management interface for all advanced storage features regardless of the capabilities of the underlying array. <br />I think you probably had enough time to examine the intuitive GUI of SVSP and understand that it is simple to manage from a small to an enterprise estate<br />this all without the need to keep changing tools to complete tasks.<br />Many customers have differing technologies from many vendors and this provides a solution for managing the sprawling estate.<br />Just keeping this inside the array has many limitations and is akin to keeping VM&#39;s confined to a single server in the server virtualisation space.<br />Also this is done at wire speed with no cache to synchronise in the network, thus enabling stretched SVSP domain across metro distances so no LUN resignaturing for VMWare when synchronously mirroing between 2 EVA&#39;s, add to this asynchronous mirroring to a third location and you have a complete business critical solution.<br />SVSP provides the ability to use different storage pools for the writable snapshot region, enabling the use of provisioning the right storage for the right task.<br />Especially usefull for test and dev environments or combined with mirroring to provide disk to disk backup and offsite presentation of the replicated disk without breaking the mirroring <br />this allows you to do regular testing of your DR without the need to break the mirrors or do a full resynch after the test &#8211; many customers don&#39;t test DR often enough because of this<br />along with the powerful scripting API you can provide a great deal of automation without the need to have a different tool for each array<br />let me know if you need more help getting it <img src='http://blog.fosketts.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> <br />Regards Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scostigan</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13754</link>
		<dc:creator>scostigan</dc:creator>
		<pubDate>Mon, 12 Oct 2009 12:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13754</guid>
		<description>Interesting that you say you just don&#039;t get SVSP&lt;br&gt;some things to consider, you a removing the binding of the host from the back end array, &lt;br&gt;thus allowing any to any data migration as you want to retire and bring in new storage technology without downtime. &lt;br&gt;A single management interface for all advanced storage features regardless of the capabilities of the underlying array. &lt;br&gt;I think you probably had enough time to examine the intuitive GUI of SVSP and understand that it is simple to manage from a small to an enterprise estate&lt;br&gt;this all without the need to keep changing tools to complete tasks.&lt;br&gt;Many customers have differing technologies from many vendors and this provides a solution for managing the sprawling estate.&lt;br&gt;Just keeping this inside the array has many limitations and is akin to keeping VM&#039;s confined to a single server in the server virtualisation space.&lt;br&gt;Also this is done at wire speed with no cache to synchronise in the network, thus enabling stretched SVSP domain across metro distances so no LUN resignaturing for VMWare when synchronously mirroing between 2 EVA&#039;s, add to this asynchronous mirroring to a third location and you have a complete business critical solution.&lt;br&gt;SVSP provides the ability to use different storage pools for the writable snapshot region, enabling the use of provisioning the right storage for the right task.&lt;br&gt;Especially usefull for test and dev environments or combined with mirroring to provide disk to disk backup and offsite presentation of the replicated disk without breaking the mirroring &lt;br&gt;this allows you to do regular testing of your DR without the need to break the mirrors or do a full resynch after the test - many customers don&#039;t test DR often enough because of this&lt;br&gt;along with the powerful scripting API you can provide a great deal of automation without the need to have a different tool for each array&lt;br&gt;let me know if you need more help getting it :-)&lt;br&gt;Regards Steve</description>
		<content:encoded><![CDATA[<p>Interesting that you say you just don&#39;t get SVSP<br />some things to consider, you a removing the binding of the host from the back end array, <br />thus allowing any to any data migration as you want to retire and bring in new storage technology without downtime. <br />A single management interface for all advanced storage features regardless of the capabilities of the underlying array. <br />I think you probably had enough time to examine the intuitive GUI of SVSP and understand that it is simple to manage from a small to an enterprise estate<br />this all without the need to keep changing tools to complete tasks.<br />Many customers have differing technologies from many vendors and this provides a solution for managing the sprawling estate.<br />Just keeping this inside the array has many limitations and is akin to keeping VM&#39;s confined to a single server in the server virtualisation space.<br />Also this is done at wire speed with no cache to synchronise in the network, thus enabling stretched SVSP domain across metro distances so no LUN resignaturing for VMWare when synchronously mirroing between 2 EVA&#39;s, add to this asynchronous mirroring to a third location and you have a complete business critical solution.<br />SVSP provides the ability to use different storage pools for the writable snapshot region, enabling the use of provisioning the right storage for the right task.<br />Especially usefull for test and dev environments or combined with mirroring to provide disk to disk backup and offsite presentation of the replicated disk without breaking the mirroring <br />this allows you to do regular testing of your DR without the need to break the mirrors or do a full resynch after the test &#8211; many customers don&#39;t test DR often enough because of this<br />along with the powerful scripting API you can provide a great deal of automation without the need to have a different tool for each array<br />let me know if you need more help getting it <img src='http://blog.fosketts.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> <br />Regards Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13748</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13748</guid>
		<description>Well, that&#039;s the thing. The MSA 2012i IS in the HP Spock and VMware databases (HCL lists) and both say that hardware iSCSI is required. I can better understand what&#039;s going on when you say VMware rewrote the iSCSI stack, but when a SAN is already on the VMware HCL, does that not mean that it IS tested and signed off?? If the HP Spock database says XYZ about a SAN, does that not mean it is tested and signed off?? The 2312i appeared about a month plus ago on the VMware SAN compatibility list for ESX 4.0, the MSA 2012i only appeared the week before last, on 9/24/09 or thereabouts. I read elsewhere that VMware updates the HCL every Wednesday, I will check both sites agian tomorrow and next Thursday, then I have to start thinking about buying these expensive iSCSI cards. &lt;br&gt;&lt;br&gt;Meanwhile, I thank you for your kind replies!! :)</description>
		<content:encoded><![CDATA[<p>Well, that&#39;s the thing. The MSA 2012i IS in the HP Spock and VMware databases (HCL lists) and both say that hardware iSCSI is required. I can better understand what&#39;s going on when you say VMware rewrote the iSCSI stack, but when a SAN is already on the VMware HCL, does that not mean that it IS tested and signed off?? If the HP Spock database says XYZ about a SAN, does that not mean it is tested and signed off?? The 2312i appeared about a month plus ago on the VMware SAN compatibility list for ESX 4.0, the MSA 2012i only appeared the week before last, on 9/24/09 or thereabouts. I read elsewhere that VMware updates the HCL every Wednesday, I will check both sites agian tomorrow and next Thursday, then I have to start thinking about buying these expensive iSCSI cards. </p>
<p>Meanwhile, I thank you for your kind replies!! <img src='http://blog.fosketts.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnmh</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13747</link>
		<dc:creator>johnmh</dc:creator>
		<pubDate>Wed, 07 Oct 2009 23:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13747</guid>
		<description>Tom,&lt;br&gt;&lt;br&gt;Sorry that&#039;s all the info I have, soon generally means as soon as it&#039;s tested and signed off. Unfortuantley I don&#039;t know what else is on the testing schedule. I do know ESX 4.0 rewrote the whole iSCSI stack so requalification was needed on some of the kit and as I said earlier the newer boxes tend to run through qualification first..</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Sorry that&#39;s all the info I have, soon generally means as soon as it&#39;s tested and signed off. Unfortuantley I don&#39;t know what else is on the testing schedule. I do know ESX 4.0 rewrote the whole iSCSI stack so requalification was needed on some of the kit and as I said earlier the newer boxes tend to run through qualification first..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13746</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 07 Oct 2009 21:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13746</guid>
		<description>Wow...this is the first new news I have had on this topic.&lt;br&gt;I asked on the blog as you suggested.&lt;br&gt;Calvin Zito kindly said he passed on my questions, I don&#039;t know what will happen.&lt;br&gt;I have also asked at HP Business Support Center but have not received any definitive replies, though upon re-reading the Spock database, I saw a mention of VMware embedded multi-path, which means that ESX 4.0 must be automatically able to see the hardware HBAs, though I am not at all an expert on SANs etc.&lt;br&gt;Would you please explain what &#039;qualification issue&#039; means and maybe even what &#039;soon&#039; means??&lt;br&gt;If &#039;soon&#039; is only a couple weeks or months, I can be patient.&lt;br&gt;Thank you, Tom</description>
		<content:encoded><![CDATA[<p>Wow&#8230;this is the first new news I have had on this topic.<br />I asked on the blog as you suggested.<br />Calvin Zito kindly said he passed on my questions, I don&#39;t know what will happen.<br />I have also asked at HP Business Support Center but have not received any definitive replies, though upon re-reading the Spock database, I saw a mention of VMware embedded multi-path, which means that ESX 4.0 must be automatically able to see the hardware HBAs, though I am not at all an expert on SANs etc.<br />Would you please explain what &#39;qualification issue&#39; means and maybe even what &#39;soon&#39; means??<br />If &#39;soon&#39; is only a couple weeks or months, I can be patient.<br />Thank you, Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnMH</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13745</link>
		<dc:creator>JohnMH</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13745</guid>
		<description>Tom,&lt;br&gt;&lt;br&gt;Had word from HP this is a qualification issue between HP &amp; VMware and should be resolved soon.</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Had word from HP this is a qualification issue between HP &#038; VMware and should be resolved soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13739</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 03 Oct 2009 16:11:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13739</guid>
		<description>I *have* looked at the Spock site. I will complain at the blog site. Thank you for the link.</description>
		<content:encoded><![CDATA[<p>I *have* looked at the Spock site. I will complain at the blog site. Thank you for the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnMH</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13734</link>
		<dc:creator>JohnMH</dc:creator>
		<pubDate>Sat, 03 Oct 2009 10:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13734</guid>
		<description>Tom,&lt;br&gt;&lt;br&gt;You should probably ask the question on the HP blog below. You can also check out the HP compatibility matrix on the spock website.&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.communities.hp.com/online/blogs/datastorage/Default.aspx&quot; rel=&quot;nofollow&quot;&gt;http://www.communities.hp.com/online/blogs/data...&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://h20272.www2.hp.com/&quot; rel=&quot;nofollow&quot;&gt;http://h20272.www2.hp.com/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>You should probably ask the question on the HP blog below. You can also check out the HP compatibility matrix on the spock website.</p>
<p><a href="http://www.communities.hp.com/online/blogs/datastorage/Default.aspx"  rel="nofollow">http://www.communities.hp.com/online/blogs/data&#8230;</a><br /><a href="http://h20272.www2.hp.com/"  rel="nofollow">http://h20272.www2.hp.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.fosketts.net/2009/10/01/hp-tech-day/comment-page-1/#comment-13733</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 02 Oct 2009 18:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2323#comment-13733</guid>
		<description>I will try ONE LAST TIME to explain...your blog destroyed my first response. That means something is broken.&lt;br&gt;The $1000 cost is per hardware iSCSI card that VMware and HP would force me to buy to have our 2012i SAN be supported for ESX 4.0 -- QLogic 2-port HBA cards.&lt;br&gt;Both VMware and HP documentation say this. To further muddy the waters, VMware support told me ALUA must be set up in the array,.and HP told me ALUA is not possible in the 2012i.&lt;br&gt;So now I am in a situation of take my chances and run ESX 4.0 on the 2012i any way I can and be unsupported or spend all this money and not know for sure if ESX 4.0 will work on the 2012i with these hardware iSCSI cards.&lt;br&gt;Very poor support from both companies so far in my efforts to gain clarity etc.&lt;br&gt;Oh, and these cards are not supported on this SAN for ESX 3.5 so I think I cannot even test!! to see what happens etc.&lt;br&gt;I used my work email in this post if you are interested in responding.&lt;br&gt;Thank you, Tom</description>
		<content:encoded><![CDATA[<p>I will try ONE LAST TIME to explain&#8230;your blog destroyed my first response. That means something is broken.<br />The $1000 cost is per hardware iSCSI card that VMware and HP would force me to buy to have our 2012i SAN be supported for ESX 4.0 &#8212; QLogic 2-port HBA cards.<br />Both VMware and HP documentation say this. To further muddy the waters, VMware support told me ALUA must be set up in the array,.and HP told me ALUA is not possible in the 2012i.<br />So now I am in a situation of take my chances and run ESX 4.0 on the 2012i any way I can and be unsupported or spend all this money and not know for sure if ESX 4.0 will work on the 2012i with these hardware iSCSI cards.<br />Very poor support from both companies so far in my efforts to gain clarity etc.<br />Oh, and these cards are not supported on this SAN for ESX 3.5 so I think I cannot even test!! to see what happens etc.<br />I used my work email in this post if you are interested in responding.<br />Thank you, Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>

