<?xml version="1.0" encoding="utf-8"?>
				<rss version="2.0">
				  <channel>
						<title><![CDATA[Disaster Recovery Planning - Blogs]]></title>
						<link>http://www.disaster-recovery-planning.org</link>
						<description />
						<language>en-us</language>
						<copyright><![CDATA[http://www.disaster-recovery-planning.org]]></copyright>
						<generator>N/A</generator>
						<webMaster>drpo@e-janco.com</webMaster>
						<lastBuildDate>Thu, 20 Nov 2008 17:16:18 MST</lastBuildDate>
						<ttl>20</ttl>

					<item>
					  <title><![CDATA[How will the recession impact your DRP and BCP process]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/17/How-will-the-recession-impact-your-DRP-and-BCP-process.html</link>
					  <description><![CDATA[As the recession takes hold some&nbsp;enterprises are failing to stay on top of&nbsp;their&nbsp;DRP and&nbsp;BCP processes.&nbsp; Is that happening at your company?]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Sat, 16 Feb 2008 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/17/How-will-the-recession-impact-your-DRP-and-BCP-process.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Age of Wireless LANs is with us]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/16/Age-of-Wireless-LANs-is-with-us.html</link>
					  <description><![CDATA[<span style="FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'; mso-fareast-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; mso-bidi-font-family: 'Times New Roman'; mso-fareast-theme-font: minor-latin; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-theme-font: minor-bidi"><font face="Arial" size="2"><a href="http://www.e-janco.com/blog.php"><img title="" height="110" alt="Blog Policy" hspace="5" src="http://www.e-janco.com/images/blog.gif" width="85" align="right" vspace="5"/></a>Because they free users from the need to be cabled to a physical network, wireless LANs are being used as an access vehicle to help businesses better collaborate. Wireless LANs can improve business process efficiencies, provide scalability, improve infrastructure costs, contribute to customer and employee satisfaction, and help resolve business continuity issues. When considering a wireless LAN implementation, users should address security, bandwidth, roaming, and interference issues.</font></span>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Wed, 30 Jan 2008 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/16/Age-of-Wireless-LANs-is-with-us.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Disk to Disk (D2D) Could be a Qucik Solution to Tape Problems]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/15/Disk-to-Disk-D2D-Could-be-a-Qucik-Solution-to-Tape-Problems.html</link>
					  <description><![CDATA[<span style="FONT-SIZE: 8pt">
<p align="left">The last few years have seen a number of information technology trends converge, transforming disk-to-disk backup (D2D) from something merely feasible into an attractive addition to the IT portfolio.</p>
<p align="left"><a href="http://www.e-janco.com/DRP_and_Security.htm" target="_blank"><img title="" height="162" alt="DRP and Security Policy Templates" hspace="5" src="http://www.disaster-recovery-planning.org/content_images/1/Disaster_Recovery_Security.gif" width="132" align="right" vspace="5" border="0"/></a>D2D technology brings many key benefits to your IT infrastructure, including shorter backup windows, faster restores, quicker nearline access, investment protection by leveraging existing tape hardware, and better backup economy through incremental backups.</p>
<p align="left">
<p align="left">For several decades, tape drives and tape media have been the preferred enterprise backup solution. But now, modern backup software supports writing to a disk file as though it was another backup device. Often this is implemented by emulating a tape device with special characteristics, allowing the disk file to easily integrate into the rest of the existing software architecture. The common term for this is virtual tape. Some backup software also supports the creation of multiple emulated devices and combining them into virtual tape libraries, referred to as&nbsp; VTL. D2D backup uses these virtual tapes to save backup data by writing to the VTL, and restores the backup data by reading from the VTL. Using hard disk drives as the underlying storage media brings all the advantages of random access, high volume manufacturing, disk reliability, RAID, and familiar technology.</p></p></span>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Tue, 15 Jan 2008 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/15/Disk-to-Disk-D2D-Could-be-a-Qucik-Solution-to-Tape-Problems.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[How Much Downtime Can You Tolerate]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/14/How-Much-Downtime-Can-You-Tolerate.html</link>
					  <description><![CDATA[
<p class="MsoPlainText" style="MARGIN: 0in 0in 0pt"><font style="FONT-SIZE: 8pt" face="Consolas">There is an increase in the number of companies and organizations requiring 24 x 365 days of <a href="http://www.e-janco.com/drp.htm" target="_blank">IT uptime</a>. In fact,&nbsp;research indicates that 36% of enterprises indicate they will incur significant revenue loss or other adverse business impact if they have even an hour or less of downtime on their mission-critical applications. Almost 15% indicate they cannot tolerate any downtime. More and more organizations of all sizes now require applications to be running and data to be always available. The needs of these organizations go far beyond simply recovery, requiring an environment that maintains business continuity during and immediately after a disaster. To make it more interesting, the number and types of applications that require this level of protection is very diverse.</font></p>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Thu, 10 Jan 2008 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/14/How-Much-Downtime-Can-You-Tolerate.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Cyber Attack Can Impact Your Disaster Plan]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/13/Cyber-Attack-Can-Impact-Your-Disaster-Plan.html</link>
					  <description><![CDATA[
<p><span style="FONT-SIZE: 8pt">A cyber attack reported last week by one of the federal government's nuclear weapons laboratories may have originated in China, according to a confidential memorandum distributed Wednesday to public and private security officials by the Department of Homeland Security. </span></p><span style="FONT-SIZE: 8pt">
<p><font size="2"><a href="http://www.e-janco.com/Security.htm"><img title="Security" height="110" alt="Security" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/Security.gif" width="85" align="left" vspace="10" border="0"/></a>Security researchers said the memorandum, which was obtained by The New York Times from an executive at a private company, included a list of Web and Internet addresses that were linked to locations in China. However, they noted that such links did not prove that the Chinese government or Chinese citizens were involved in the attacks. In the past, intruders have compromised computers in China and then used them to disguise their true location. </font></p>
<p><font size="2">Officials at the lab, Oak Ridge National Laboratory in Tennessee, said the attacks did not compromise classified information, though they acknowledged that they were still working to understand the full extent of the intrusion. </font></p>
<p>- <font face="Arial" size="2"><a href="http://www.e-janco.com/Security.htm" target="_blank"><font size="2">more info</font></a></font><font size="2">&nbsp;</font></p></span>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Fri, 14 Dec 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/13/Cyber-Attack-Can-Impact-Your-Disaster-Plan.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[How does the Vista &quot;Kill Switch&quot; Impact the DRP]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/12/How-does-the-Vista-quotKill-Switchquot-Impact-the-DRP.html</link>
					  <description><![CDATA[With the elimination of the Vista "kill switch" feature will there be any impact on your Disaster Recovery / Business Continuity Plan.<br/><br/>We say no, as a matter of fact this should simplify the Disaster Recovery Process with the elimination of that feature.&nbsp;&nbsp; What are your thoughts?]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Sat, 08 Dec 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/12/How-does-the-Vista-quotKill-Switchquot-Impact-the-DRP.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Key Components of a Disaster Plan]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/11/Key-Components-of-a-Disaster-Plan.html</link>
					  <description><![CDATA[
<p><span style="FONT-SIZE: 8pt"><a href="http://www.itproductivity.org/Disaster-Recovery-Planning.htm" target="_blank"><img title="Disaster Recovery Plan  Template" height="110" alt="Disaster Recovery Plan  Template" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/Disaster_Recovery.gif" width="85" align="right" vspace="10" border="0"/></a>Disaster Recovery / Business Continuity and security experts at Janco have identified several critical steps in planning for disaster and subsequent recovery. </span></p><span style="FONT-SIZE: 8pt">
<p class="MsoListParagraphCxSpFirst" style="MARGIN: 0in 0in 0pt 31.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list: Ignore">1.<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Determine how the event will impact four key areas:</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 49.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l1 level2 lfo2"><span style="FONT-FAMILY: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span style="mso-list: Ignore">&middot;<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>People: How will you notify, evacuate, transport and care for employees?</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 49.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l1 level2 lfo2"><span style="FONT-FAMILY: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span style="mso-list: Ignore">&middot;<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Property: What equipment will you need and how will you source it?</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 49.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l1 level2 lfo2"><span style="FONT-FAMILY: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span style="mso-list: Ignore">&middot;<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Systems: What portions of your computing and telecommunications infrastructure must be duplicated immediately? How much downtime can your operation tolerate?</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 49.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l1 level2 lfo2"><span style="FONT-FAMILY: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol"><span style="mso-list: Ignore">&middot;<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Data: What data is critical to run your business, and how will you recover critical data that is lost?</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 31.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list: Ignore">2.<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Determine which data, applications and systems must be restored and in what sequence. Prioritize systems as critical, vital, sensitive or noncritical, and talk to users at all levels to make sure youre not overlooking any crucial systems.</p>
<p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0in 0in 0pt 31.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list: Ignore">3.<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span style="mso-spacerun: yes">&nbsp;</span>Analyze the hardware and software configurations that support critical business functions and isolate possible points of failure.</p>
<p class="MsoListParagraphCxSpLast" style="MARGIN: 0in 0in 0pt 31.5pt; TEXT-INDENT: -0.25in; mso-layout-grid-align: none; mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list: Ignore">4.<span style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Quantify hourly costs based on interruptions of these systems.</p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none">Each of these is included in the Disaster Recovery / Business Continuity Template that can be found at <a href="http://www.itproductivity.org/Disaster-Recovery-Planning.htm">http://www.itproductivity.org/Disaster-Recovery-Planning.htm</a> </p>
<p><a href="http://www.itproductivity.org/Disaster-Recovery-Planning.htm" target="_blank">more info</a></p></span>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Wed, 05 Dec 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/11/Key-Components-of-a-Disaster-Plan.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Recovery point and recovery time objectives]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/10/Recovery-point-and-recovery-time-objectives.html</link>
					  <description><![CDATA[<span style="FONT-SIZE: 8pt; FONT-FAMILY: ">
<p align="left">Recovery point objective (RPO) refers to the amount of data loss a customer can tolerate, speci<font face="FuturaBk" size="2">fi</font><font face="FuturaBk" size="2">cally the point in time to which your enterprise must be able to recover the data. Some&nbsp;enterprises require an RPO of &#8220;zero&#8221;. That means the&nbsp;enterprise cannot lose a single </font><i><font face="FuturaBk-Italic" size="2">committed </font></i><font face="FuturaBk" size="2">transaction in the event of a site failure; they must be able to recover the data back to the zero minute of the time of the disaster. There are implications to setting up an RPO of zero. The replication solution will require synchronous replication (explained in detail later in this section) and may impact performance of the application being replicated.</font></p><font face="FuturaBk" size="2">
<p align="left"><a href="http://www.itproductivity.org/DRP_and_Security.htm" target="_blank"><img title="DRP Security" height="162" alt="DRP Security" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/Disaster_Recovery_Security.gif" width="132" align="left" vspace="10" border="0"/></a>An RPO of greater than zero, for example 30 minutes, can be handled differently. An RPO of 30 minutes means the customer can tolerate losing the last 30 minutes of transactions in the event of a site failure. If the disaster occurred at 12:00, the customer must be able to recover the data to at least 11:30 (30 minutes prior to the disaster). This can most likely be accomplished with asynchronous replication with minimal performance impact to the application. In this situation, careful planning and monitoring of the write-history log is essential to support the expected RPO.</p>
<p align="left"><a href="http://www.e-janco.com/audit_template.html" target="_blank"><img title="DRP Security Audit" height="250" alt="DRP Security Audit" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/templateaudit.gif" width="200" align="right" vspace="10" border="0"/></a>A&nbsp;RPO can only be determined by their business rules and other governances of their environment. The customer must weigh the risk of data loss in a higher RPO against the cost and performance impact of a zero RPO.</p>
<p align="left">Recovery time objective (RTO) refers to the amount of time it takes a customer to get their backup site up and running after a complete failure at the primary site. Most customers have an RTO of <font face="FuturaBk" size="2">anywhere from 15 minutes to 8 hours, though the average is about 2 hours. This includes the time to failover the replicated LUNs (logical Unit Number) to the backup EVA (Enterprise Virtural Array) , recover the backup database and bring it online, and redirect any applications to the backup database server. A faster RTO can usually be accomplished by prestaging the backup site to the greatest extent possible.</font></p></font></span>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Tue, 04 Dec 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/10/Recovery-point-and-recovery-time-objectives.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[What is Business Continuity]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/9/What-is-Business-Continuity.html</link>
					  <description><![CDATA[
<p style="FONT-SIZE: 8pt"><a href="Business Continuity" target="_blank"><img title="Business Continuity" height="110" alt="Business Continuity" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/Disaster_Recovery.gif" width="85" align="left" vspace="10" border="0"/></a>In the volatile world we live in today, any business in the world could be jeopardised by any number of external influences, how can you prepare your business correctly to cope with the unexpected crises that could occur at any time With the western world being on a constantly heightened security alert, natural disasters occurring more and more frequently and other threats that have not even been predicted, today's world is a risky place to live in </p>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Wed, 28 Nov 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/9/What-is-Business-Continuity.html</guid>
					</item>

				

					<item>
					  <title><![CDATA[Email is a high risk application that DRP needs to consider first]]></title>
					  <link>http://www.disaster-recovery-planning.org/blogs/8/Email-is-a-high-risk-application-that-DRP-needs-to-consider-first.html</link>
					  <description><![CDATA[<font size="2">
<p align="left"><a href="http://www.itproductivity.org/Disaster-Recovery-Planning.htm" target="_blank"><img title="Business Continuity" height="110" alt="Business Continuity" hspace="10" src="http://www.disaster-recovery-planning.org/content_images/1/Disaster_Recovery.gif" width="85" align="right" vspace="10" border="0"/></a>In order to effectively use email as a business tool, these security issues must be addressed from a technical, managerial, and regulatory perspective. Unfortunately, there is no magic formula, product, or service that will handle all of these aspects of email. At least in the foreseeable future, email security will require some form of human and/or manual intervention. </p>
<p>There are, however, some highly effective solutions that can help with these issues from the executive level all the way to end users. A smart decision for the practical businessperson is to automate as much of the technical, managerial, and regulatory requirements as possible. This is especially important for small and medium businesses that are dealing with fewer IT and security resources. </p></font>]]></description>
					  <author>no@spam.com (Site Administrator)</author>
					  <pubDate>Tue, 27 Nov 2007 00:00:00 MST</pubDate>
					 <guid isPermaLink="true">http://www.disaster-recovery-planning.org/blogs/8/Email-is-a-high-risk-application-that-DRP-needs-to-consider-first.html</guid>
					</item>

				
				  </channel>
				</rss>
			