1. Business Continuity & Disaster Recovery Daniel Griggs Solutions Architect Ohio Valley September 30, 2008

2. 2Agenda » Disaster defined/Types of disasters » Who is impacted? » What should we do? » Where should we recover? » When should we test? » How will we keep our costs down? » Your Partner for Business Continuity Solutions » How can we help? » Thank You!

3. 3 Disaster Recovery » Disaster defined ●An adverse, unfortunate and unforeseen event! ●Being down ●Being unable to service/support customers » What is the largest enemy in a disaster? ●Having an untested plan ●Time!

4. 4 Types of Disasters » Natural (fire, flood, wind, earthquake, etc.) » Malicious intent (virus, burglary, vandalism, etc.) » Localized outages: ●Hardware ●Power ●Telecom ●Software ●Data Corruption

5. 5 » Customers? » Staff? » The Business could be at risk! » Disaster Examples ●How many businesses never reopened after Katrina? › Over 80% of companies affected went out of business within 18 months as a consequence Source: Survive, 2007Source: Survive, 2007 Who is Impacted?

6. 6 Top Disaster Recovery Concerns » Planning for the disaster » Resources to build and test BCP and DR plans » Communication of the plan » Inherent infrastructure problems » Backup challenges » Archival strategies » Replication strategies

7. 7 What Should we do? » Conduct a Business Impact Analysis (BIA) » Create a Business Continuity Planning Office (BCPO) » Establish Incident Management team (IMT) » Establish a Life Safety – Emergency Response Team (ERT) » Define DR plan owner ●Define DR strategy

8. 8 Business Continuity Planning Office (BCPO) – Plan Integration IS Recovery (DRP) Business Continuity Plan (BCP) Life Safety- Emergency Response Team (ERT) Incident Management Team (IMT) Executives

9. 9 Disaster Recovery ●Source: IT Performance Engineering & Measurement Strategies: Quantifying Performance Loss, Meta Lost Revenue Per Hour

10. 10 Disaster Recovery » Where should we recover? ●Cold site ●Hot site ●Production site and Dev/QA site » When should we test? ●Should test as often as possible (at least twice per year) ●Involve business in testing ●Increase complexity of each test

11. 11 Why Should we worry » Risk + Probability of failure ●Local failure (fault tolerance). Most likely scenario. › Disk › HBA › SAN Switch › SAN › Core Switch ●Proximity - location increases risk of incident › Highway › Airport (Memphis) › Water

12. 12 DR Requirements Match your internal fault tolerance and DR capabilities to: ●The overall availability requirements of your company › Do you need 99.999s? ●Recovery Time Objective (RTO) › Determined via BIA › Base your plan on lowest RTO ●Data loss tolerance - RPO › Determined via BIA › Base your plan on lowest RPO

13. 13Examples » RTO = 4 hrs, RPO = 0, Availability = 99.999 ●All local infrastructure fault tolerant ●Critical applications are clustered ●Synchronous replication to hot site ●Tape backup plan for recovery; tapes sent off-site every day » RTO = 72 hrs, RPO = 24 hours, Availability = 99.5 ●SAN fault tolerant; core fault tolerant ●Little to no clustering ●Tape backup plan for recovery at a cold site; tapes sent off-site every day

14. 14 How will we keep our costs down? » Virtualize ●Virtualization greatly simplifies DR ●Virtualization reduces the cost of DR » Reducing Backup Pain ●De-duplication › 20x data reduction › Extend disk backup ●Backup to disk (VTL) › Eliminate tapes in remote sites › Enable fast backup AND recovery › Use tapes for long-term archival only

15. 15 How will we keep our costs down? » Improving efficiency of SAN ●Document Management Policy/Practice ●Archiving (based on policy) › Save $1000s on tapes while still protecting your data › Archiving will allow you to quickly restore business critical data › By using a tiered storage solution, you will have already separated your business critical data from the rest › Improve TCO of SAN » Use DR site for Dev/QA ●Production replicates real time to DR site ●Dev/QA replicates at a reduced interval back to SAN at production site

16. 16Archiving » Store more intelligently ●Classify and tier ●Archive inactive data ●Eliminate redundant data ●Streamline backups ●Utilize snaps for incr. changes ●Virtualize servers Archive Data Backup Data Clones Remote Volumes Snaps Production Data Tier 3 Tier 2 Tier 1

17. 17Archiving » iSCSI ●Least expensive connectivity ●Easy to replicate ●Pay as you grow technology ●Fast deployment

18. 18 In the Face of a Disaster – Case #1 » What if everything is lost? » CDW’s Enterprise Configuration Center can be your DR Site » In your time of need, you HAVE to have fast response » Detroit-area customer ●Fire on Friday ●Weekend re-build and re-image ●Delivery

19. 19 In the Face of a Disaster – Case #1 » CDW drop-shipped ●Imaged desktops and notebooks ●Fully-configured › Routers › Switches › Firewalls ●Wireless APs ●Installed server racks

20. 20 In the Face of a Disaster – Case #2 » What’s your backup plan? » Environmental consulting firm ●10-ft. under water ●Had developed plan with CDW

21. 21 In the Face of a Disaster – Case #2 » BC/DR Plan ●Hot site in Mississippi › Relocation within 48 hours ●Asynchronous replication – SAN ●MPLS (IP-VPN) › Meshed environment » “My CDW team is like an extension of my IT department”

22. 22 Your Partner for BC Solutions We Assess » CDW Specialists ●Server ●Storage ●Networking ●Power/Cooling ●Software » Onsite Virtualization partners » Assessments We Implement » CDW Services ●Custom Onsite Solutions » CDW Technology Architect Team » Rack configuration services » Custom Imaging services » Asset tagging We Support » 24x7x365 tech support » Priority vendor support » Multiple options – phone, chat, email » Knowledgeable » Responsive

23. 23Questions Glen Coleman Enterprise Architect, Security Officer Ohio Department of Health Daniel Griggs Solutions Architect, CDW