LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
DRP – Mainly where the IT comes into play and involves: Planning and implementation of procedures and facilities for use when essential systems are not available for a prolonged period of time</li></li></ul><li>What is BCP (Business Continuity Planning) ?<br /><ul><li>Business continuity planning
Is the creation and validation of a practiced logistical plan for how an organization will recover and restore partially or completely interrupted critical (urgent) functions within a predetermined time after a disaster or extended disruption. The logistical plan is called a business continuity plan.
BCP is working out how to stay in business in the event of disaster. Incidents include local incidents like building fires, regional incidents like earthquakes, or national incidents like pandemic illnesses.</li></li></ul><li>A few Statistics<br /><ul><li>In 2009 Symantec released the results of its fifth annual Global IT Disaster Recovery survey;
According to the report, 93% of organizations have had to execute their DR Plans and the average cost:
The average budget for disaster recovery initiatives worldwideis $50 million USD – Not a lot really!
Average time it takes to "achieve skeleton operations after an outage" is 3hours.
Average time to be fully "up and running after an outage," the average is 4hours, states the report. </li></li></ul><li>A few Statistics - continued<br /><ul><li>Executive-level involvement in DR plans is rising.
In 2007, 55% of respondents reported DR committees involved the CIO, CTO or IT director
DR "becoming a competitive differentiator“ within organizations – especially in the financial sector
Also driven by budgets, Upper management making sure IT spends wisely in the current economy </li></li></ul><li>Disaster Recovery Planning Objectives<br /><ul><li>Develop the ability to recover key business functions following a disaster
Recover systems based on a timeline as defined by an Internal Audit of operations
Financials (5 days)</li></li></ul><li>What is mainly affected?<br /><ul><li>A Business Impact Analysis is essential to determine what core business functions would be most critical to restore following a disaster.
IT Infrastructure (to support the business applications above)</li></li></ul><li>What Systems or Services are Required?<br /><ul><li>Outline all business critical needs for restoration of services within the timeline determined by the analysis.
Testing failover</li></li></ul><li>Bandwidth – The Replication Challenge<br /><ul><li>If you're lucky enough to get 70% of the bandwidth usable! you're likely to see transfer rates for a dedicated connection similar to those in the table below. </li></li></ul><li>Bandwidth - Continued<br /><ul><li>Reasons for loss of bandwidth:
The provider. In most cases with your standard T1 at 1.5MB your lucky to get 1.3MB then you have…
The asynchronous replication engine is often based on a protocol, protocol converter
Fewer hours spent creating and maintaining DR plans and processes
Significantly reduced cost of DR tests; eliminates IT staff overtime and application impact
Recovery in a matter of hours, not days or weeks – greatly reducing the financial exposure a company faces during a major outage
The following captures an estimate of the cost savings provided by SRM when used to recover from a major outage or disaster</li></ul>Company that does $25M in revenue a year = ~$96k/weekday. Assume that SRM can achieve RTO of 12 hours instead of 72 hours compared to traditional DR plan.<br />Value of Lost Revenue<br />Value of Lost Time by Workers<br />$96,153<br />2.5<br />X<br />+<br />500<br />2.5<br />=<br />X<br />$300/day<br />X<br />X<br />$ 615,385(per disaster)<br />X<br />Days of<br />faster recovery<br />Number of<br />workers<br />Lost revenue per workday<br />Days of<br />faster recovery<br />Cost of worker<br />wages<br />
Failover Automation<br /><ul><li>Detect site failures
Symantec continues to say, that only 15% report that they never experienced a failure in test. </li></li></ul><li>Q&A<br /><ul><li>Any questions?</li></li></ul><li>Contact Information<br />Ultan Kinahan<br />Business Continuity & Disaster Recovery<br />Kinahan@live.com<br />