Taking the Disaster out of Disaster Recovery

Taking the Disaster out of Disaster Recovery

Agenda Challenges of Traditional DR Properties of Virtualization for DR Using VMware Virtualization in DR 10 Steps to better DR using VMware Virtualization Product Overview and Next Steps

What we hear is this familiar? Customers We don t have a DR plan for mission critical x86 systems it would be too expensive and complex It is very difficult to test our DR plan because of all the extra hardware, configuration and special processes In our last disaster recovery test we missed our recovery objectives by days Analysts Only 31% of CIO s surveyed rate their plans as extremely or very effective (IDG) 40% of all companies that experience a major disaster will go out of business if they cannot gain access to their data within 24 hours (Gartner)

DR Challenges Today Challenges of Traditional DR: Infrastructure Prod Application Bound to HW 5-10% utilized DR Application 1:1 App bound to OS, OS bound to HW x86 OS OS files local storage WAN x86 OS OS files local storage Storage Storage Multiple slow processes to transfer data to DR site for OS, application installation, configuration, data files Requires 1:1 duplication Expensive of servers and Complex and infrastructure at DR site Makes x86 physical DR strategies complex and expensive DR site: what a waste of servers, power, storage & space!

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

Traditional DR approach: Waste of servers, networking, storage Waste of space, power, cooling, connectivity High maintenance cost: Change in Primary -> 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 not work!

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

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

VMware Virtualization Enablers for DR Encapsulation System Apps Data Physical Server = files in VFMS Encapsulate entire systems in simple files Simplify backup and replication Simplify copying and cloning of systems Simplify provisioning Simply moving a file! No need to start from scratch

VMware Virtualization Enablers for DR Isolation App OS Batch Job App OS DR Test App OS VMware Infrastructure Provide easier testing of DR plan Utilize DR hardware for other tasks Leverage resource pools to separate workload groups (won t interfere with each other) Each virtual machine is isolated from other virtual machines within same host

VMware Virtualization Enablers for DR Partitioning % Utilization Byconsolidating servers Boost utilization Provide significant cost savings Safely run multiple virtual machines simultaneously on a single physical server

Data and System Protection Physical vs. Virtual Data and system protection with Physical infrastructure Separate processes for protecting data and system disks Require identical hardware for guaranteed restore Complex processes to ensure protection System configuration System Data Data and system protection with VMware infrastructure - eliminates these challenges Same process for data and system disks Entire system stored as data Hardware-independent virtual machines are easy to restore to any hardware System, data, system config

Backup Options with VMware App Backup Agent App Backup Agent Agent-less! OS Service Console OS Service Console Backup Agent tape Backup Server In-VM In-Console VCB Agent in each VM Same architecture as physical system backup File-level incremental backup possible Any storage Agent in Service Console Simplified backup of fulldisk images only Any storage Less granular Consolidated Backup - Agent on Proxy Server Move backup out of VM Provide LAN-free backup Requires FC SAN Pre-integrated with 3 rd party backup products

VMware Consolidated Backup How it Works Centralized file and image level backup 1 2 1. Take VM Snapshot 2. Mount SAN Snapshot 3. Backup files or disk images with leading backup tools 3 Move backup out of the virtual machine Run midday backups LAN Free Integrated with 3 rd party backup

Replication with VMware: Host-Based Replication Site Failure CA XoSoft, EMC Replistor, DoubleTake, VizionCore ESX Replicator others WAN WAN 1. Replicate data to DR site 2. At failure Boot VM at remote site using replicated data 3. Done! Source VMFS SLA s = moderate Target VMFS

Replication with VMware: Array-Based Replication DR SITE PRIMARY Site Failure WAN WANoror Dark DarkFiber Fiber Array-Based Replication (SRDF, SnapMirror, etc.) Target VMFS Source VMFS SLA s = High

Protecting Physical Machines with Virtual Machines Another Option Physical to Virtual Recovery Convert physical machines to VMs using VMware Converter, Platespin, LeoStream Can use to protect against local physical server/storage failures Consider when physical servers in production are in lock-down mode No need to reinstall and rebuild Costs significantly less to build your DR Primary site imaging imaging P2V P2V conversion conversion Secondary Site imaging P2V conversion WAN replication

Real VMware Customer Results Business Metric Server Utilization Consolidation Ratio Server Provisioning Time Planned Downtime Unplanned Downtime Time to Recovery Payback (Break-Even) TCO Results From 4X- 5X Increase From 2:1 up to 30:1 > 60% reduction > 95% reduction > 30% reduction Down to Minutes < 6 months 30-70% reduction Source: VMware customers surveyed post-use of VMware products.

10 Steps to Viable Disaster Recovery: Assess 1. Assess disaster recovery requirements Which services need to be recoverable Impact of downtime for key services What are the RTO and RPO requirements of key services 2. Assess application requirements What applications are required to provide key services What are the dependencies between applications

10 Steps to Viable Disaster Recovery: Plan 3. Determine what to virtualize < 4 physical CPU utilization < 16 GB of RAM used < 5 adapters (NIC s, SCSI interfaces, etc.) 4. Determine disaster recovery architecture Backup and recovery Replication Own site vs. co-location site 5. Select hardware and software components e.g. servers, storage, backup software Check VMware HCL s where appropriate

10 Steps to Viable Disaster Recovery: Build 6. Convert and consolidate Use VMware Converter or third-party tools to convert physical systems to virtual machines 7. Set up backup and/or replication Backup Separate system disk and application data Perform file-level and image-level backups Replication Choose type of replication Select disks and LUN s to replicate

10 Steps to Viable Disaster Recovery: Manage 8. Test Test frequently, at least twice per year Think about having surprise tests Clone production virtual machines for realistic testing Use resource pools and VLAN s to isolate test environment 9. Optimize Use idle recovery hardware for other tasks Enable DRS to optimize utilization and performance Enable VMware HA for protection from local server failures 10.Document What people are expected to be involved What is recovery process for each protection tier What needs to be tested and validated during recovery

DR : The Killer App for Virtualization! Press Best Disaster Recovery Product of 2006 (TechTarget) No SKU Customers 55% of customers using virtualization for BC/DR N=2265 55% 2006 Customer Survey (n=2265) 85% use VMware in production; 43% set as a default policy for production servers

Four Core Solutions Enabled by VMware Infrastructure Infrastructure & Capacity Optimization (Server Consolidation) Business Continuity Workload Mobility Disaster Recovery and HA VMware Infrastructure 3 Solutions Virtual SW Lifecycle Automation Enterprise Desktop VMware Converter Virtual Center VMFS VMotion DRS ESX Server HA VCB Workstation Lab Manager VDI ACE Products

VMware Infrastructure for Disaster Recovery VMware Virtual SMP Enables single VM to use up to 4 physical processors simultaneously Virtual Machine File System (VMFS) High performance cluster file system. Allows multiple ESX Servers to access same VM storage concurrently VMware Virtual Center Centralize management of VM infrastructure VMware Converter Automates conversion of physical to virtual machines (physical-virtual) VMware Consolidated Backup Centralized agent less backup for VM s VMware High Availability Cost effective automatic restart of virtual machines in case of server failure VMware Distributed Resource Scheduler Dynamic and intelligent balancing of computing resources across resource pools based on pre-defined rules. VMware VMotion Moves live, running VM s from one host to another while maintaining continuous service availability. VMware ESX Server 3.0 Production-proven virtualization layer that resources into multiple virtual machines (VM s) Bare Metal Basic VMware Infrastructure for DR Optional Components VMware Infrastructure for DR

Thank You!!