1 / 23

DR Challenges of Traditional DR

DR Challenges of Traditional DR. Production. DR. Application. Bound to HW 5-10% utilized. Application. 1:1. OS. OS. App bound to OS, OS bound to HW. WAN. x86. x86. OS files. OS files. local storage. local storage. Storage. Storage. DR is EXPENSIVE and COMPLEX!

catori
Download Presentation

DR Challenges of Traditional DR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DR Challenges of Traditional DR Production DR Application • Bound to HW • 5-10% utilized Application 1:1 OS OS App bound to OS, OS bound to HW WAN x86 x86 OS files OS files local storage local storage Storage Storage DR is EXPENSIVE and COMPLEX! Waste of servers, storage, power & space at DR site!

  2. DR Challenges of traditional DR Challenges of Traditional DR: Recovery Process Prod DR “Boot & Pray” cd, tape or ghost image WAN Application Application OS OS x86 x86 OS files OS files local storage local storage • Complex to physically recover OS, applications & data • Separate processes for system and application data • OS & applications have dependencies on hardware configuration • Tier 2 & 3 applications left unprotected, adding to Tier 1 RTO risk Repl process: OS – Images App Data-Replication SW: SAN-SAN, OS based Storage Storage Just Tier 1! Slow and Unreliable Process

  3. Drawbacks of traditional DR • Waste of resources: servers, networking, storage, space, power, cooling, connectivity... • High maintenance cost: any Change in Primary -> needs Change in DR (HW/SW) • Hard or impossible DR simulation (conflicts with the primary) • Hard or impossible alternative usage (quality, test, development) • Final Result: When needed will often not work!

  4. What is Server Virtualization VMware server virtualization packages hardware, OS, and applications into a portable virtual machine package Before Virtualization After Virtualization • Software tied to hardware • Single OS image per machine • One application workload per OS • Multiple workloads per machine • Software independent of hardware • System, data, apps are files

  5. VMware Virtualization Enablers for DR Hardware Independence • Eliminate need for 1:1 hardware duplication for DR • Eliminate risk of hardware “configuration drift”(disparate sites) • Re-use older servers for DR Run a virtual machine on any server without modification

  6. The Challenges – as Seen in the Field Customer challenges: • Low budget • Lack of experienced personnel • Solution is complex and slow to deploy Customer profile: • Customer who otherwise would not implement DR solution because of high costs • Customer who is looking for solutions for department or branch office • Virtualization newbie looking for add-on to an existing DR solution • Customer who is under the time pressure

  7. The Solution: DR in a Box Main Features: • Affordable • Easy • Pre-packaged • Flexible

  8. What is the KEY • Packaged solutions are usually less expensive than traditional approach via consulting • Reusable solutions and deliverables instead of time intensive customizations • Redeploy a reinforced solution instead of designing a new solution • Use less experienced staff for the implementation • Flexibility is one of the main customer demands, so it needs to be addressed: DR-in-a-box is designed as a set of a few solution blocks. Each block is a packaged solution designed to solve a sub-set of the problem. Blocks may be combined to build a complete disaster recovery solution.

  9. DR in a Box Solution Blocks – Outline

  10. DR for VirtualCenter - What is THE KEY VirtualCenter Server is almost a stateless application. However the replication is required for the following files: • SSL certificateFlex • License files • VirtualCenter Configuration file • Optionally -upgrade files Additionally, each ESX Server stores the IP address of the VirtualCenter Server in the agent configuration file • IP address change is necessary to bring the standby VirtualCenter Server in production

  11. DR for VirtualCenter – Solution Design

  12. DR for VirtualCenter - Disaster Recovery

  13. Active / Active with VMware HA – Solution Design

  14. Active / Active with VMware HA Solution Design - Disaster Recovery

  15. Active / Passive DR Site – Solution Design

  16. Active / Passive DR Solution Design - Disaster Recovery

  17. Guest OS Storage Replication – Solution Design

  18. Guest OS Storage Replication Solution Design - Disaster Recovery

  19. Network Reconfiguration –Solution Design

  20. Network Reconfiguration Solution Design -Disaster Recovery

  21. Solution Blocks – Outline

  22. Questions?

  23. Thank You !!

More Related