Presentation is loading. Please wait.

Presentation is loading. Please wait.

Disaster Recovery with VMware Infrastructure VMware Infrastructure for Rapid, Reliable, and Cost-Effective Disaster Recovery.

Similar presentations


Presentation on theme: "Disaster Recovery with VMware Infrastructure VMware Infrastructure for Rapid, Reliable, and Cost-Effective Disaster Recovery."— Presentation transcript:

1 Disaster Recovery with VMware Infrastructure VMware Infrastructure for Rapid, Reliable, and Cost-Effective Disaster Recovery

2 Agenda Challenges of Traditional DR Properties of Virtualization for DR Using VMware Virtualization in DR SRM Technical Overview

3 What We Hear…Is This Familiar? We dont 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 Only 31% of CIOs 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)

4 DR Pain Points Lack of a reliable disaster recovery plan 27-30% of business have no disaster recovery plan (VMworld, Imation) Inability to meet RTO and RPO requirements with current plan Business needs and/or regulatory needs Need to improve RTO from days to minutes or hours Need to improve RPO from 24 hours to 1 hour or less Idle hardware at recovery site Unable to instantly repurpose machines at the secondary site Management effort required to maintain recovery site Need to maintain system and application images at secondary site Usually only data is regularly and cleanly updated

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

6 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 Slow and Unreliable Process DR Challenges Today cd, tape or ghost image Application OS x86 OS files local storage Storage WAN Application OS x86 OS files local storage Storage Prod Boot & Pray DR Challenges of Traditional DR: Recovery

7 Agenda Challenges of Traditional DR Properties of Virtualization for DR Using VMware Virtualization in DR SRM Technical Overview

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

9 What is Server Virtualization Before VirtualizationAfter Virtualization VMware server virtualization packages hardware, OS, and applications into a portable virtual machine package 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

10 Copyright © 2006 VMware, Inc. All rights reserved. VMware Virtualization Enablers for DR Hardware Independence Run a virtual machine on any server without modification Eliminate need for 1:1 hardware duplication for DR Eliminate risk of hardware configuration drift Re-use older servers for DR

11 Copyright © 2006 VMware, Inc. All rights reserved. VMware Virtualization Enablers for DR Encapsulation Encapsulate entire systems in simple files Simplify backup and replication Simplify copying and cloning of systems Simplify provisioning System Apps = files in VFMS Physical Server Data

12 Copyright © 2006 VMware, Inc. All rights reserved. VMware Virtualization Enablers for DR Isolation Each virtual machine is isolated from other virtual machines Provide easier testing of DR plan Utilize DR hardware for other tasks Leverage resource pools to separate workload groups VMware Infrastructure OS App OS App OS App Batch Job DR Test

13 Copyright © 2006 VMware, Inc. All rights reserved. VMware Virtualization Enablers for DR Partitioning Safely run multiple virtual machines simultaneously on a single physical server Consolidate servers Boost utilization Provide significant cost savings % Utilization

14 Agenda Challenges of Traditional DR Properties of Virtualization for DR Using VMware Virtualization in DR Data and system protection Replication DR testing Protecting physical servers with virtual machines SRM Technical Overview

15 VMware Availability Products And Features Avoid planned outagesQuick recovery from unplanned outages Component Server Storage Data N/A Site VMware HA VMotion, DRS + Maintenance Mode NIC Teaming, Multipathing Encapsulation, VCBStorage VMotion Encapsulation, boot from shared storage, instant reprovisioning, HW independence, resource pools, snapshots, VLANs Encapsulation, VCB VMware Site Recovery Manager

16 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 Data and system protection with VMware Infrastructure 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 System Data System configuration

17 Backup Options with VMware – Reduce Backup Windows Agent in Service Console Simplified backup of full- disk images Any storage Agent in each VM Same architecture as physical system backup File-level incremental backup possible Any storage Service Console App OS Backup Agent Service Console Backup Server tape App OS Backup Agent Consolidated Backup - Agent on Proxy Server Move backup out of VM Provide LAN-free backup Eliminate backup windows Pre-integrated with 3 rd party backup products OS In-VM In-Console VCB

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

19 Replication with VMware: Array-Based Replication WAN or Dark Fiber WAN or Dark Fiber Array-Based Replication PRIMARY DR SITE Site Failure Source VMFS Target VMFS Storage array

20 Simpler Disaster Recovery Testing with Virtualization 1.Snapshot and clone replicated data to create testing VMs 2.Connect test VMs to an isolated network 3.Power up testing VMs to validate recovery 4.Delete VM clones used for testing SA N Target VMFS DR Site OS.image Appln.image Data.image Data. OS Application 15 GHz 9 GHz Powered On DR VMs - Rapid DR setup and removal - Dual-use of DR site for batch, test and other workloads Live DR Test DR Replicated Data Snapshot

21 Recovery Process in a Virtualized Environment RTO of minutes to a few hours, not days to weeks! Configure hardware Install OS Configure OS Install backup agent Start Single-step automatic recovery Restore VM Power on VM Example recovery process comparison P-P V-V 40+ hrs < 4+ hrs

22 VMware Site Recovery Manager: Technical Overview July 2008 VMware

23 Agenda Introduction and Key Concepts Site Recovery Manager 1.0 Prerequisites and SAN Integration Site Recovery Manager Workflows Site Recovery Manager Roles and Privileges Alarms and Site Status Monitoring Summary

24 What is a Disaster? Complete loss of a data center for an extended period of time Declaration of a disaster usually requires consensus from multiple parts of the organization (at the C*O level) What is not a disaster? Failure of an individual host A temporary service interruption

25 The Current State of Physical Disaster Recovery DR services tiered according to business needs Physical DR is challenging Maintain identical hardware at both locations Apply upgrades and patches in parallel Little automation Error-prone and difficult to test TierRPORTOCost IImmediate $$$ II24+ hrs.48+ hrs.$$ III7+ days5+ days$

26 Advantages of Virtual Disaster Recovery Virtual machines are portable Virtual hardware can be automatically configured Test and failover can be automated (minimizes human error) The need for idle hardware is reduced Costs are lowered, and the quality of service is raised

27 Simplifies and automates disaster recovery workflows: Setup, testing, failover Turns manual recovery runbooks into automated recovery plans Provides central management of recovery plans from VirtualCenter Introducing VMware Site Recovery Manager Works with VMware Infrastructure to make disaster recovery rapid, reliable, manageable, affordable Site Recovery Manager leverages VMware Infrastructure to deliver advanced disaster recovery management and automation

28 Protected Site Recovery Site VirtualCenter Site Recovery Manager VirtualCenter Site Recovery Manager Datastore Groups Array Replication Datastore Groups X Site Recovery Manager at a Glance Protected VMs powered on become unavailable online in Protected Site offline Site A Site B Recovery Site Protected Site Supports bi- directional site protection

29 Server Side Components * Site 1 VC Server 1 SRM Server 1 Storage Replication Adapter SRM 1 DB VCMS 1 DB Block Replication SW Site 2 VC Server 2 SRM Server 2 Storage Replication Adapter SRM 2 DB VCMS 2 DB Block Replication SW Array 1 Array 2 * Note: Conceptual drawing only. Site Recovery Manager Server may run on another system than VCMS

30 Site Recovery Manager Concept Relationship Cheat Sheet SiteConceptRelationship ProtectedLUNIndivisible unit of storage that can be replicated ProtectedDatastoreContains one or more LUNs (i.e. VMFS) ProtectedDatastore Groups Auto-generated collection of one or more datastores. Indivisible unit or storage failover. ProtectedProtection Group Collection of all VMs stored in a datastore group RecoveryRecovery PlanContains one or more protection groups

31 Key Concepts And Their Relationships Protection Group 3 Protection Group 2 Protection Group 1 Datastore Group 3 Datastore Group 2 Datastore Group 1 LUN 1 LUN 2 LUN 3 LUN 4 LUN 5 VMFS 1 VMFS 2 VMFS 4 VMFS 3 Recovery Plan 1 (Whole Site) Protection Groups: Recovery Plan 2 (Subset) Protection Groups: Protected SiteRecovery Site Protection Group 1 Protection Group 2 Protection Group 3 Protection Group 1

32 Array Integration with Site Recovery Manager Vendor-specific scripts support: Array discovery Replicated LUN discovery Test initiation (simulated failover in an isolated environment) Failover initiation (actual failover of services to the recovery site) In cooperation with VMware and with the full support of VMware the storage vendors create the storage replication adapters for their respective storage arrays

33 Protected Site Recovery Site VirtualCenter Site Recovery Manager VirtualCenter Site Recovery Manager VMware Site Recovery Manager Licensing Site 2Site 1 SRM licensed per CPU socket on the ESX server that hosts the protected virtual machines in the Protected Site SRM Protected VMs VMs not protected by Site Recovery Manager

34 Safety Tip: DNS Validation – The Rule of Four Validate DNS is working as expected by performing the following DNS lookups for the VC,SRM and ESX servers Short name Long name Reverse Forward

35 Site Recovery Manager 1.0 Prerequisites ESX 3.0.2, ESX 3.5 VirtualCenter (VC) server version 2.5 installed at the protected site and at the recovery site Site Recovery Manager server installed at the protected and at the recovery site Site Recovery Manager plug-in installed on the VMware Infrastructure Clients that will access the protected and recovery site Network configuration that allows TCP connectivity between VC servers and SRM servers An Oracle or SQL Server database that uses ODBC for connectivity in the protected site and in the recovery site A Site Recovery Manager license file installed on the VC license server at the protected site and at the recovery site Pre-configured array-based replication between the protected site and the recovery site

36 Site Recovery Manager Installation Workflow At the protected site the following activities are completed: Installation of the SRM server Installation of the SRM Plugin into the VI Client Installation of the Storage Replication Adapter (SRA) At the recovery site the following activities are completed: Installation of the SRM server Installation of the SRM Plugin into the VI Client * Installation of the Storage Replication Adapter (SRA) It is important to complete the workflows in the order detailed in this presentation * Note: Optional step, only required if a different instance of the VI Client is used to access the recovery site

37 Protected and Recovery Site Datacenters PROTECTED SITE RECOVERY SITE

38 Site Recovery Manager User Interface Local and Paired Site Protection Setup Recovery Setup SRM UI Access

39 Setup Workflow – Protection Site At the protection site the following setup activities are completed: The user pairs the SRM servers at the protected and recovery sites Security certificates are established between the SRM servers and the VC servers Certificates that are not properly signed will result in the Yellow Warnings Signs. Reciprocity will still be established allowing you to continue to the next step in the workflow.

40 Setup Workflow – Protection Site (continued) Array Managers Configuration Select the correct Manager Type from the Manager type drop down box Storage Partner Participation VMware provides the SRA specification Storage Partners create the SRA Storage Partners test the SRA VMware review the SRA test results SRA support with SRM granted if all test are passed

41 SRM identifies available arrays in the Protection and Recovery Side and the replicated datastores and determines the datastore groups Protection Side Array Discovery Recovery Side Array Discovery Replicated Datastores and Datastore Groups Setup Workflow – Protection Site (continued)

42 Using the Inventory Preferences Mapper, the user maps resources in the protected site to their counterparts in the recovery site.

43 Setup Workflow – Protection Site (continued) A protection group is a group of VMs that will be failed over together to the recovery site Working through the Protection Group wizard you will need to select a temporary location for placeholder VM configuration files for the protected VMs at the recovery site.

44 Setup Workflow – Protection Site (continued) Working through the Protection Group wizard a user selects which VMs need to be protected and assigns them to a protection group The creation of a protection group results in VC inventory updates in the recovery site

45 Setup Workflow – Recovery Site At the recovery site the following setup activity is completed: The user creates a recovery plan which is associated to a single or multiple protection groups

46 Site Recovery Manager Recovery Plan VM Shutdown High Priority VM Recovery Prepare Storage High Priority VM Shutdown Normal Priority VM Recovery

47 Site Recovery Manager Recovery Plan (continued) Site Recovery Manager Recovery Plan Benefits: Turn manual BC/DR run books into an automated process Specify the steps of the recovery process in VirtualCenter Provide a way to test your BC/DR plan in an isolated environment at the recovery site without impacting the protected VMs in the protected site Low Priority VM Recovery Post Test Cleanup Storage Reset

48 Testing a Recovery Plan SRM enables you to Test a recovery plan by simulating a failover with zero downtime to the protected VMs in the protected site

49 Testing a Recovery Plan (continued) Status Success Errors Waiting for Input Recovery Only Test Only Success

50 Executing an Actual Failover WARNING - Executing an actual failover will permanently alter virtual machines and infrastructure of both the protected and recovery sites

51 Executing an Actual Failover (continued) WARNING - Executing an actual failover will permanently alter virtual machines and infrastructure of both the protected and recovery sites WARNING - Failback to the protected site is a not an automated process in SRM 1.0

52 SRM performs a Datastore re-signature SRM will automatically perform a re-signature on the Datastores in the Recovery Site that were replicated from the SRM Protected Site LVM.EnableResignature=1 With a re-signature - Datastore names will change to snapxxxx_datastorename, for example snap shared-san-1 snap shared-san-2 WARNING - The re-signature of the target datastore has implications during a failback (resync) of data back to the SRM Protected Site

53 Failback Options with Site Recovery Manager 1.0 SRM 1.0 does not provide a push-button automated failback process Failback Options Without SRM (no Recovery Plan, no Testing capabilities, no audit trail) Unregister the protected virtual machines in the Protected Site VC Work with your storage team, reverse data replication VM re-inventory in Protected Site VC, restart and re-ip (manual or scripted) With SRM (Recovery Plan, Test before Recovery, built-in audit trail) Delete the protection groups in the Protected Site VC Unregister the protected virtual machines in the Protected Site VC Work with your storage team, reverse data replication Leverage SRM, complete SRM workflows in the reverse direction from Recovery Site back to the Protected Site Repeat the above steps from the Protected Site back to the Recovery Site to complete the re-protection of the virtual machines in the Protected Site

54 Default Roles and Privileges in Site Recovery Manager

55 Alarms and Site Status Monitoring SRM will support the following alarm notification actions: Send to specified address Send SNMP trap to VC trap receivers Execute specified command on VC host We recommend you complete setup of alarm notifications for: Remote Site Down Remote Site Ping Failed Replication Group Removed Recovery Plan Destroyed License Server Unreachable

56 Site Recovery Manager Server Monitoring SRM will raise VC events for the following conditions: Disk Space Low CPU use exceeded limit Memory low Remote Site not responding Remote Site heartbeat failed Recovery Plan Test started, ended, succeeded, failed, or cancelled Virtual Machine Recovery started, ended, succeeded, failed, or reports a warning

57 Site Recovery Manager Core Benefits Expand disaster recovery protection Now any workload in a VM can be protected with minimal incremental effort and cost Reduce time to recovery As soon as disaster is declared, a single button kicks off recovery sequence for hundreds of VMs Increase reliability of recovery Replication of system state ensures a VM has all it needs to startup Hardware independence eliminates failures due to different hardware Easier testing based off of actual failover sequence allows more frequent and more realistic tests

58 Summary Site Recovery Manager Leverages VMware Infrastructure to Make Disaster Recovery Rapid Automate disaster recovery process Eliminate complexities of traditional recovery Reliable Ensure proper execution of recovery plan Enable easier, more frequent tests Manageable Centrally manage recovery plans Make plans dynamic to match environment Affordable Utilize recovery site infrastructure Reduce management costs

59 Backup Slides

60 Protected Site Topology Map

61 Setup Workflow – Recovery Site VC Updates The creation of the protection group results in VC Inventory updates in the recovery site. Protected VMs app_vm1 to app_vm12 are created in the VC inventory in the recovery site with the creation of their respective protection groups in the protected site

62 Questions?


Download ppt "Disaster Recovery with VMware Infrastructure VMware Infrastructure for Rapid, Reliable, and Cost-Effective Disaster Recovery."

Similar presentations


Ads by Google