<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>ITBE: Message List - Disaster Recovery Execution</title>
    <link>http://www.itbusinessedge.com/cm/community/kn?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Thu, 11 Jun 2009 15:26:17 GMT</pubDate>
    <generator>Clearspace 2.5.5 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-11T15:26:17Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1474?tstart=0#1474</link>
      <description>I agree.   an old plan is no plan at all. There should be benchmarks to determine when a plan is reviewed and updated. Whether these would be based on Annual review, or some system or process change, or both, I think would differ by company. Either way,</description>
      <pubDate>Thu, 11 Jun 2009 15:26:17 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1474?tstart=0#1474</guid>
      <dc:date>2009-06-11T15:26:17Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1473?tstart=0#1473</link>
      <description>"The best-laid plans of mice and men often go awry" &amp;nbsp; I think this certainly applies. The fact is, that even with fully trained staff, and a comprehensive plan the potential for unexpected circumstance to throw a wrench in the works is huge. It is</description>
      <pubDate>Thu, 11 Jun 2009 14:57:41 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1473?tstart=0#1473</guid>
      <dc:date>2009-06-11T14:57:41Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1472?tstart=0#1472</link>
      <description>There is no guarantee that the plan will be executed as it was planned, but with careful preparation there is a very good chance that things will go according to what we want. Besides testing and documenting the process, the members must understand</description>
      <pubDate>Wed, 10 Jun 2009 05:55:28 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1472?tstart=0#1472</guid>
      <dc:date>2009-06-10T05:55:28Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1471?tstart=0#1471</link>
      <description>I agreed Ritchie, testing is one of the key factors. A plan can be well written, but if the testing environment is not fully equipped to simulate the actual environment during a testing, the plan might prove futile when it is time for execution. As</description>
      <pubDate>Wed, 10 Jun 2009 05:53:53 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1471?tstart=0#1471</guid>
      <dc:date>2009-06-10T05:53:53Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1470?tstart=0#1470</link>
      <description>No matter how well we plan things; there will always be a chance that something can go wrong.  All we can do is try our best to look ahead and plan for anything that could go wrong.  There is no guarantee how well the plan will be executed. It depends</description>
      <pubDate>Wed, 10 Jun 2009 05:47:02 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1470?tstart=0#1470</guid>
      <dc:date>2009-06-10T05:47:02Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1469?tstart=0#1469</link>
      <description>Executing a DR plan when it needs to be executed is the paramount reason for creating the plan. If the plan cannot be executed when needed, there is no need to create it. Frequent testing and training are some major ways to ensure that a DR is executed</description>
      <pubDate>Wed, 10 Jun 2009 05:41:05 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1469?tstart=0#1469</guid>
      <dc:date>2009-06-10T05:41:05Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1468?tstart=0#1468</link>
      <description>Well said warrick, I think the success will come in the form of team members and Management  making it a routine practice of doing the test, maybe one per quarter. Like the Emergency Alert Test they do on the radio or like the Fire drills that Some</description>
      <pubDate>Tue, 09 Jun 2009 11:38:34 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1468?tstart=0#1468</guid>
      <dc:date>2009-06-09T11:38:34Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1467?tstart=0#1467</link>
      <description>Good plans will often attempt to provide controls for the decision making process in order to ensure predictability as well as sound and prudent logic. One good way of providing this logic would be to utilize flow charts, these basic charts help to</description>
      <pubDate>Tue, 09 Jun 2009 04:51:09 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1467?tstart=0#1467</guid>
      <dc:date>2009-06-09T04:51:09Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1466?tstart=0#1466</link>
      <description>There are no guarantees that any plan will ever be executed according to the script. There are simpy too many variables and an infinite number of possbilities based on a multitude of factors. No plan can account for EVERYTHING, instead prudent</description>
      <pubDate>Tue, 09 Jun 2009 04:33:03 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1466?tstart=0#1466</guid>
      <dc:date>2009-06-09T04:33:03Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1465?tstart=0#1465</link>
      <description>Chris, I agree and I know I mentioned the testing and training but you bring up the good point that the DR professionals can't make sure it is executed 100%.  The team and senior management have to take that responsibility.  What if a consultant created</description>
      <pubDate>Mon, 08 Jun 2009 20:06:01 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1465?tstart=0#1465</guid>
      <dc:date>2009-06-08T20:06:01Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1462?tstart=0#1462</link>
      <description>Well, we as DR professionals, don't. It is not up to us to make sure the plan is executed "to the nines". It is up to the team leaders and senior management to assure that the plan is executed to the highest standards. The plan can be 110% thourough for</description>
      <pubDate>Mon, 08 Jun 2009 15:20:49 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1462?tstart=0#1462</guid>
      <dc:date>2009-06-08T15:20:49Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1461?tstart=0#1461</link>
      <description>As always, Andre' is spot-on! If there is support from senior managenet the rest of the company should comply. Then if the training is complete, to the plan specifications and reveals any issues that would support up-dating the plan, we are coming full</description>
      <pubDate>Mon, 08 Jun 2009 15:16:59 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1461?tstart=0#1461</guid>
      <dc:date>2009-06-08T15:16:59Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1460?tstart=0#1460</link>
      <description>You make a good point Emmanul. A plan that isn't updated or reviewd on an regular basis is a plan that may fail. Plus, you should account for personnel leaving the company, on vacation, out sick, and have other personnel trained to fill the roles and</description>
      <pubDate>Mon, 08 Jun 2009 13:41:46 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1460?tstart=0#1460</guid>
      <dc:date>2009-06-08T13:41:46Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1459?tstart=0#1459</link>
      <description>There are three main objectives, if met, that will ensure the DR plan gets executed as planned: (1) total suppprt from senior management (2) training of personnel involved in the execution of the plan and (3) testing of the DR plan. If these three</description>
      <pubDate>Mon, 08 Jun 2009 13:34:43 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1459?tstart=0#1459</guid>
      <dc:date>2009-06-08T13:34:43Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1458?tstart=0#1458</link>
      <description>i Agree Dave, In addition to testing, The plan must always be updated regularly. as things change in the company, people leave and new people come in, the plan should be updated to reflect those changes.</description>
      <pubDate>Mon, 08 Jun 2009 04:42:06 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1458?tstart=0#1458</guid>
      <dc:date>2009-06-08T04:42:06Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1457?tstart=0#1457</link>
      <description>I don't think there is any way to be 100% positive that a plan will get implemented correctly, but that doesn't mean that we shouldn't try to get it to that point.  I feel that the most important thing we can do to make sure it is implemented as planed</description>
      <pubDate>Mon, 08 Jun 2009 03:57:32 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1457?tstart=0#1457</guid>
      <dc:date>2009-06-08T03:57:32Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Disaster Recovery Execution</title>
      <link>http://www.itbusinessedge.com/cm/message/1451?tstart=0#1451</link>
      <description>We as DR professionals take the time to create an awesome plan. How do we guarantee that when it needs to be executed, it gets executed as it was planned?</description>
      <pubDate>Thu, 04 Jun 2009 17:31:47 GMT</pubDate>
      <author>webadmin@itbusinessedge.com</author>
      <guid>http://www.itbusinessedge.com/cm/message/1451?tstart=0#1451</guid>
      <dc:date>2009-06-04T17:31:47Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>16</clearspace:replyCount>
    </item>
  </channel>
</rss>

