 




<?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: Disaster Recovery &#8211; when to declare one?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 06:03:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: lightmike</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/#comment-73819</link>
		<dc:creator>lightmike</dc:creator>
		<pubDate>Mon, 15 Feb 2010 15:57:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-73819</guid>
		<description><![CDATA[Absolutely let the requirements dictate the solution as well as the activation plan.  &lt;b&gt;It&#039;s business processes that need the technology.&lt;/b&gt;  If a business process is mission critical it needs to be expressed in a tolerable amount of downtime, or response time objective (RTO).   When does the disruption of the business process hurt the long term marketshare or financial viability of the organization?.  If it is a really short period of time, then it is the requirement that dictates having a multi-site active cluster of services (&quot;hot site&quot;) that fail over without human intervention.  Your question suggests you have built a &quot;warm site&quot; that requires a manual decision to transfer processing.  This may be acceptable from a requirements (RTO) and cost-benefit standpoint (hot sites are inherently more expensive), but your business processes should dictate the number of minutes or hours you have to resume the business process that is dependent on the technology.  Then you have your answer, if fixing the problem locally is estimated to be within your RTO guidelines, then fit it...If the estimated fix time exceeds the RTO, you declare and fire up the warm site.]]></description>
		<content:encoded><![CDATA[<p>Absolutely let the requirements dictate the solution as well as the activation plan.  <b>It&#8217;s business processes that need the technology.</b>  If a business process is mission critical it needs to be expressed in a tolerable amount of downtime, or response time objective (RTO).   When does the disruption of the business process hurt the long term marketshare or financial viability of the organization?.  If it is a really short period of time, then it is the requirement that dictates having a multi-site active cluster of services (&#8220;hot site&#8221;) that fail over without human intervention.  Your question suggests you have built a &#8220;warm site&#8221; that requires a manual decision to transfer processing.  This may be acceptable from a requirements (RTO) and cost-benefit standpoint (hot sites are inherently more expensive), but your business processes should dictate the number of minutes or hours you have to resume the business process that is dependent on the technology.  Then you have your answer, if fixing the problem locally is estimated to be within your RTO guidelines, then fit it&#8230;If the estimated fix time exceeds the RTO, you declare and fire up the warm site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevinbeaver</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/#comment-72984</link>
		<dc:creator>kevinbeaver</dc:creator>
		<pubDate>Sun, 24 Jan 2010 16:08:32 +0000</pubDate>
		<guid isPermaLink="false">#comment-72984</guid>
		<description><![CDATA[Bottom line - How&#039;s it going to impact your business? 

This is why performing a business impact analysis and documenting your plans before such issues arise is so important. Here&#039;s &lt;a href=&quot;http://securityonwheels.blogspot.com/2009/07/good-business-impact-analysis-template.html&quot;&gt;a good resource&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>Bottom line &#8211; How&#8217;s it going to impact your business? </p>
<p>This is why performing a business impact analysis and documenting your plans before such issues arise is so important. Here&#8217;s <a href="http://securityonwheels.blogspot.com/2009/07/good-business-impact-analysis-template.html">a good resource</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jennymack</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/#comment-72838</link>
		<dc:creator>jennymack</dc:creator>
		<pubDate>Wed, 20 Jan 2010 15:00:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-72838</guid>
		<description><![CDATA[CharlieBrowne and Meandyou,

Great, informative answers here. Thank you!

Jenny
Community Manager]]></description>
		<content:encoded><![CDATA[<p>CharlieBrowne and Meandyou,</p>
<p>Great, informative answers here. Thank you!</p>
<p>Jenny<br />
Community Manager</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meandyou</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/disaster-recovery-when-to-declare-one/#comment-72794</link>
		<dc:creator>meandyou</dc:creator>
		<pubDate>Tue, 19 Jan 2010 15:29:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-72794</guid>
		<description><![CDATA[The procedures for our D/R plan state that if the recovery time at our local site will exceed 24 hours a disaster is declared and we go offsite.
 
We do not have a &quot;hot&quot; site for d/r.  We have access to other computer systems, but we have to build them from the ground up.  It takes about 24 hours to do this.  
 
Hence,  if it will take longer than 24 hours to recovey at local site, we go to d/r site.  We have not done this for real.  But we do go offsite and rebuild critical apps twice per year.]]></description>
		<content:encoded><![CDATA[<p>The procedures for our D/R plan state that if the recovery time at our local site will exceed 24 hours a disaster is declared and we go offsite.</p>
<p>We do not have a &#8220;hot&#8221; site for d/r.  We have access to other computer systems, but we have to build them from the ground up.  It takes about 24 hours to do this.  </p>
<p>Hence,  if it will take longer than 24 hours to recovey at local site, we go to d/r site.  We have not done this for real.  But we do go offsite and rebuild critical apps twice per year.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.014 seconds using memcached
Object Caching 310/313 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 06:52:37 -->