<?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: Averting Disaster With the EPO Button</title>
	<atom:link href="http://www.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/</link>
	<description>News and analysis about data centers, cloud computing, managed hosting and disaster recovery</description>
	<lastBuildDate>Mon, 13 Feb 2012 17:24:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: chuck goolsbee</title>
		<link>http://www.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/comment-page-1/#comment-94</link>
		<dc:creator>chuck goolsbee</dc:creator>
		<pubDate>Tue, 08 May 2007 05:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://dev.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/#comment-94</guid>
		<description>Johnny, the only way to make sabotage via EPO impossible is to eliminate the EPO.

I&#039;d wager a sushi lunch that for every one justified use of an EPO, that there are over 19 incorrect/accidental/sabotage EPO hits. For all the attention we datacenter designer/operators give to absurdly remote possibilities such as &quot;terrorist attack&quot;, or &quot;major earthquake&quot; the reality is that our number one risk is just plain old, completely un-sexy human error. Go figure.

--chuck


</description>
		<content:encoded><![CDATA[<p>Johnny, the only way to make sabotage via EPO impossible is to eliminate the EPO.</p>
<p>I&#8217;d wager a sushi lunch that for every one justified use of an EPO, that there are over 19 incorrect/accidental/sabotage EPO hits. For all the attention we datacenter designer/operators give to absurdly remote possibilities such as &#8220;terrorist attack&#8221;, or &#8220;major earthquake&#8221; the reality is that our number one risk is just plain old, completely un-sexy human error. Go figure.</p>
<p>&#8211;chuck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny Mnemonic</title>
		<link>http://www.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/comment-page-1/#comment-93</link>
		<dc:creator>Johnny Mnemonic</dc:creator>
		<pubDate>Tue, 08 May 2007 00:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://dev.datacenterknowledge.com/archives/2007/05/07/averting-disaster-with-the-epo-button/#comment-93</guid>
		<description>none of the above advice addressed the issue encountered with the lead in article:  deliberate sabotage.  Can such a thing be stopped, while allowing safety personnel access in time of emergency?
</description>
		<content:encoded><![CDATA[<p>none of the above advice addressed the issue encountered with the lead in article:  deliberate sabotage.  Can such a thing be stopped, while allowing safety personnel access in time of emergency?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

