More Related Content Similar to Disaster Recovery is Dead Similar to Disaster Recovery is Dead (20) Disaster Recovery is Dead3. Question 1 of 7 Organizations should lay out a five-year plan with a recovery time objective that is ________a. Less than two hoursb. Going to improve over timec. The same as what you have now © 2010 All rights reserved 4. Question 2 of 7 Of the 50% to 70% of organizations that develop IT disaster recovery plans, fewer than ____ actually test those plans.a. One quarterb. One thirdc. One half © 2010 All rights reserved 5. Question 3 of 7 44% of disaster recovery planners polled haven't told anybody that a DR plan exists in their organization.TrueFalse © 2010 All rights reserved 6. Question 4 of 7 How do current budget constraints change IT disaster recovery discussions with other parts of the business?a. They don’t -- IT should proceed as it has before.b. It makes it more important to involve other business departments.c. It makes it less important to involve other business departments. © 2010 All rights reserved 7. Question 5 of 7 The test of an IT disaster recovery plan came fast and furiously last year a gas and electric company, when flood waters swept over its Cedar Rapids, Iowa, territory. What technology, not touted as a big piece of the IT disaster recovery plan, came to the rescue?a. Voice over Internet Protocolb. Desktop virtualizationc. Duplication services © 2010 All rights reserved 8. Question 6 of 7 The recession is putting a squeeze on budgets for outsourcing disaster recovery services. As such, CIOs are turning to _________ to reduce floor space at their leased recovery sites, according to providers of IT disaster recovery services.a. Server virtualizationb. Cloud computingc. Contract renegotiation © 2010 All rights reserved 9. Question 7 of 7 – Done! How are companies using cloud computing for IT disaster recovery outsourcing? a. They’re increasing the number of licensees with access to DR applications.b. They’re moving mission-critical applications to a cloud environment.c. They’re creating carbon copies of applications. © 2010 All rights reserved 10. Disaster Recovery: what have we learned? Budget-minded small to midsized businesses (SMBs) once viewed business continuity (BC) planning as an expensive luxury. Not anymore. Upgrading disaster recovery (DR) capabilities is a major priority for 56% of IT decision makers in the U.S. and Europe, according to Forrester Research Inc.‘s. While companies think they’re immune to any long-term outage, more that one-fourth of companies have experienced a disruption in the last 5 years, averaging eight hours, or one business day. Source: Comdisco Vulnerability index The U.S. Department of Homeland Security says one in four businesses won't reopen following a disaster. © 2010 All rights reserved 11. The Plan: What is a DR Plan? Backup Tapes Document Software Contracts Recovery site Server Virtualization None of the above …an ounce of prevention is worth a terabyte of cure © 2010 All rights reserved 12. The Plan: What are the risks? Enterprise disaster Priority? Frequency? Local Failure © 2010 All rights reserved 13. The Plan: Types of Disaster Recovery Denial Bunker Copy Nuclear Active …all companies have a fully functioning disaster recovery plan, the only difference is the result the plan achieves © 2010 All rights reserved 14. The Plan: It’s the business Backups Disaster Recovery Business Continuity Too often, IT staffs have discussed IT disaster recovery in terms of recovering servers rather than business value 15. The Plan: Metrics Recovery Time Objective - Time required to recover critical systems to a functional state, often assumed to be “back to normal” for those systems designated as mission critical. Recovery Point Objective - Point in time to which the information has been restored when the RTO has elapsed and is dependent upon what is available from an offsite data storage location. "Are you trying to avoid employee inconvenience with your requested service levels?" 16. BIA: just study it right? Categorize Applications? Silo or interdependence Prioritize Impact? Everything is critical Replicate data? Is everything in sync? Immediate or deferred Opps, although more and more shops technically have all of their data replicated to a DR location, it is not readily usable by applications because it is not in sync. As a result, database administrators and application specialists need to spend additional hours, sometimes days, reconciling data and rolling databases back to bring the various data components into alignment. By the time this effort is complete, the desired recovery window has long since been exceeded. A B M O P A B Y Z M Y Z O P V Y Z 17. The Plan: the hard part is not the box The most common mistake businesses make when determining service-level requirements is trying to keep the business running as if nothing happened. 18. Secrets to Success Build resiliency into the design - Keep the architecture simple. Build before planning Reverse the offsite co-location so that the primary location is remote and the recovery is local. Include key vendors in the plan so that they can provide assistance. Use offshore resources to daily validate and bring current secondary sites on a daily basis – routine failovers. Make high availability the responsibility of everyone – business and IT. © 2010 All rights reserved 19. Secrets to Success: The key You have to make sure your disaster recovery plan will work with or without the internal key people who developed it. If the director in charge of financial ERP applications wrote the plan, for example, ask the business intelligence manager to test the recovery. © 2010 All rights reserved 20. Secrets to Failures Depend upon familiar local resources Plan before building Use complex technology that inserts more moving parts into the daily operations Prepare thick complex manuals. Designate a special recovery team View the recovery in terms of hardware Test the process annually over a 1-2 day period. Forget unique needs of legacy applications. Assume each application is an independent silo © 2010 All rights reserved 21. Cost: where to spend money Too often, IT staffs have discussed IT disaster recovery in terms of recovering servers rather than business value © 2010 All rights reserved 22. Cost: How to spend too much Overprotect data Fail to maintain disaster recovery plans Test disaster recovery plans too often Overlook the benefits of server virtualization Reluctance to renegotiate with disaster recovery service providers Rely on technology as a silver bullet Engage a consultancy to do a detailed plan © 2010 All rights reserved 24. Cost: How to Save Money Identify all of the costs Determine the assumptions Review the cost allocation Build the recovery cost into the implementation © 2010 All rights reserved 25. Security: Can recovery be a disaster? How to get data to facility? How to recover licenses? How to recover keys? Where are passwords? What happens to data after the test? Were any data transmissions logged? © 2010 All rights reserved 26. Executive Checklist What constitutes a disaster? Do all senior managers understand their role in the event of a disaster? How will the interim business be managed? How will public relations be managed? How will staff communications be managed? How will customers react? Do they really want to pay for .9999? What are the core business deliveries? What can be performed through alternative manual means? How much will downtime affect the share price and market confidence? How will the recovery effort be staffed? What is the resiliency of the solutions purchased? What is the PII exposure during a recovery effort? © 2010 All rights reserved 27. Recovery: evolution in progress Storage Backup Tapes Hardware Recovery Recovery Sites Virtualization Replication Business Application Implementation © 2010 All rights reserved 33. Blueprints for High Availability: Designing Resilient Distributed Systems by Evan Marcus© 2010 All rights reserved