<?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 for Wire Turf</title>
	<atom:link href="http://www.wireturf.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wireturf.com</link>
	<description></description>
	<lastBuildDate>Wed, 12 Oct 2011 06:31:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by shawn</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-127</link>
		<dc:creator>shawn</dc:creator>
		<pubDate>Wed, 12 Oct 2011 06:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-127</guid>
		<description>Same here...been down since yesterday.  I like how their &quot;system status&quot; page says that all systems are operational.  They must mean by Intermedia&#039;s standards.</description>
		<content:encoded><![CDATA[<p>Same here&#8230;been down since yesterday.  I like how their &#8220;system status&#8221; page says that all systems are operational.  They must mean by Intermedia&#8217;s standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by Jim</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-126</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 11 Oct 2011 14:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-126</guid>
		<description>And going on 24 hours of outage for us.  Not acceptable given this is the same explanation (SAN Array Failure) given last time this happened.  Fool me once...</description>
		<content:encoded><![CDATA[<p>And going on 24 hours of outage for us.  Not acceptable given this is the same explanation (SAN Array Failure) given last time this happened.  Fool me once&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by mookie</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-125</link>
		<dc:creator>mookie</dc:creator>
		<pubDate>Tue, 11 Oct 2011 11:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-125</guid>
		<description>6 more hours of SAN related outage yesterday.</description>
		<content:encoded><![CDATA[<p>6 more hours of SAN related outage yesterday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on First Impressions using Google+ by Josh Schneider</title>
		<link>http://www.wireturf.com/2011/07/11/first-impressions-using-google/comment-page-1/#comment-57</link>
		<dc:creator>Josh Schneider</dc:creator>
		<pubDate>Mon, 11 Jul 2011 13:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=223#comment-57</guid>
		<description>Hi David,  long time no speak.  Hope you are doing well and don&#039;t miss Razorgator too much.  I would love to give Google+ a shot.  Shoot me an invite if you have an extra.</description>
		<content:encoded><![CDATA[<p>Hi David,  long time no speak.  Hope you are doing well and don&#8217;t miss Razorgator too much.  I would love to give Google+ a shot.  Shoot me an invite if you have an extra.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by Joel</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-55</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Sun, 31 Oct 2010 08:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-55</guid>
		<description>Intermedia is DOWN now (early Sunday morning Oct 31).</description>
		<content:encoded><![CDATA[<p>Intermedia is DOWN now (early Sunday morning Oct 31).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by Chris</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-52</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 25 May 2010 01:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-52</guid>
		<description>maybe off topic here, but does anyone have a good solution to move from intermedia? I am tired of answering the question, what is wrong with our email now. I have installed microsoft exchange 2010 and have actually started migrating people, but the task of downloading the pst files from intermedia is no fun.</description>
		<content:encoded><![CDATA[<p>maybe off topic here, but does anyone have a good solution to move from intermedia? I am tired of answering the question, what is wrong with our email now. I have installed microsoft exchange 2010 and have actually started migrating people, but the task of downloading the pst files from intermedia is no fun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by Bo</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-51</link>
		<dc:creator>Bo</dc:creator>
		<pubDate>Fri, 07 May 2010 03:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-51</guid>
		<description>Hi David,

How&#039;s life?

Heard you left OleOle? Is everything going well with you.

Bo</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>How&#8217;s life?</p>
<p>Heard you left OleOle? Is everything going well with you.</p>
<p>Bo</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by John Martin</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-50</link>
		<dc:creator>John Martin</dc:creator>
		<pubDate>Tue, 27 Apr 2010 10:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-50</guid>
		<description>*Disclosure I Work for an EMC Competitor*

To be fair to EMC, the system in the initial failure did continue to operate but at a degraded service level. This is a characteristic of all modular storage arrays that work in high availability pairs. The level of degradation depends on the make of the array and the settings used, and it appears that Expedia took the option of choosing a configuration that put data preservation ahead of performance. Unfortunately this choice which is understandable had unpleasant and unforseen consequences.

What surprises me is that the impact of failover either wasnt tested (which is really hard to do in a multi-tenant environment), or mitigated by only using half the possible performance of the array.

Having said that, even when only using half the possible performance on a mid-range arrays,  maintaining that performance when half the array fails requires that write caching remains on, which is a dangerous practice because if the second controller fails, cached data can be lost.

If I were intermedia, I&#039;d seriously consider looking for a SAN that is either easier to test under failure conditions, or doesnt lose the majority of its performance when one of the components fails.

Given the additional outages that have happened since, I&#039;d expect that they&#039;d be doing that as a matter of urgency.</description>
		<content:encoded><![CDATA[<p>*Disclosure I Work for an EMC Competitor*</p>
<p>To be fair to EMC, the system in the initial failure did continue to operate but at a degraded service level. This is a characteristic of all modular storage arrays that work in high availability pairs. The level of degradation depends on the make of the array and the settings used, and it appears that Expedia took the option of choosing a configuration that put data preservation ahead of performance. Unfortunately this choice which is understandable had unpleasant and unforseen consequences.</p>
<p>What surprises me is that the impact of failover either wasnt tested (which is really hard to do in a multi-tenant environment), or mitigated by only using half the possible performance of the array.</p>
<p>Having said that, even when only using half the possible performance on a mid-range arrays,  maintaining that performance when half the array fails requires that write caching remains on, which is a dangerous practice because if the second controller fails, cached data can be lost.</p>
<p>If I were intermedia, I&#8217;d seriously consider looking for a SAN that is either easier to test under failure conditions, or doesnt lose the majority of its performance when one of the components fails.</p>
<p>Given the additional outages that have happened since, I&#8217;d expect that they&#8217;d be doing that as a matter of urgency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by Eric</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-47</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-47</guid>
		<description>Yes, at present it&#039;s only one server cluster that&#039;s down- EXCH020  - but it is down HARD and of course that&#039;s the one we&#039;re on. They had to stop accepting inbound mail connections. 2nd day without business email. Charming.</description>
		<content:encoded><![CDATA[<p>Yes, at present it&#8217;s only one server cluster that&#8217;s down- EXCH020  &#8211; but it is down HARD and of course that&#8217;s the one we&#8217;re on. They had to stop accepting inbound mail connections. 2nd day without business email. Charming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In the aftermath of Intermedia&#8217;s extended outage, an important lesson to be learned for SAS providers by David</title>
		<link>http://www.wireturf.com/2010/03/12/in-the-aftermath-of-intermedias-extended-outage-an-important-lesson-to-be-learned/comment-page-1/#comment-46</link>
		<dc:creator>David</dc:creator>
		<pubDate>Fri, 16 Apr 2010 15:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.wireturf.com/?p=141#comment-46</guid>
		<description>yikes! 2 days running is totally unacceptable.</description>
		<content:encoded><![CDATA[<p>yikes! 2 days running is totally unacceptable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

