1. © 2009 VMware Inc. All rights reserved vCenter Site Recovery Manager 5 How to achieve the simplest and most reliable disaster protection for all your applications

2. 2 Confidential Agenda  Introducing vCenter Site Recover Manager 5.0  What’s New In Site Recovery Manager 5.0  SRM Architecture & Workflows  vSphere Replication  Running DR Drills & Testing with SRM 5  SRM Recovery & Planned Migration  SRM Advanced Settings  SRM Editions & Licensing

3. 3 Confidential Tradeoffs Of Traditional Business Continuity Solutions Middleware / Java Oracle RAC Oracle DataGuard DB Mirroring MS Clustering DB Access Groups CCR / SCR App Server Cluster Session State Replication Backup Data replication Application-level availability silos: Complex and expensive Data protection services: Longer RTOs and RPOs

4. 4 Confidential VMware Improves Business Continuity At All Levels Local Availability  vSphere High Availability  vSphere Fault Tolerance  vMotion and Storage vMotion Data Protection  vSphere Data Recovery  Storage APIs for Data Protection Local SiteFailover Site Disaster Recovery  vCenter Site Recovery Manager  Includes vSphere Replication New in 2011 Improved in 2011 vSphere Improved in 2011

5. 5 Challenges of Traditional Disaster Recovery Expensive Complex Recovery Plans ? ? ? ? ? ? ? ? Unreliable Failovers Apps Hosts Storage Network Software Hosts Storage Facilities >$10K per app Failure to meet business requirements Long RTOs – days to weeks Too much time and resources consumed

6. 6 vSphere Provides The Best Foundation For Disaster Recovery Flexible Infrastructure Eliminate need for identical hardware across sites Enable waterfalling of equipment to recovery site Simple Application Protection Entire system – including application, OS, and data – is stored as virtual machine files Entire system can be protected with data protection tools Cost-Efficient Infrastructure Reduced hardware requirements at recovery site Use recovery hardware to run low-priority apps Encapsulation Consolidation Hardware Independence vSphere

7. 7 Simple and Reliable DR with vSphere and SRM

8. 8 vCenter Site Recovery Manager Ensures Simple, Reliable DR Provide cost-efficient replication Built-in vSphere Replication Broad support for storage-based replication Simplify management of recovery and migration plans Replace manual runbooks with centralized recovery plans From weeks to minutes to set up new plan Automate failover and migration processes Enable frequent non-disruptive testing Ensure automated failover and migration Automate failback processes Site Recovery Manager Complements vSphere to provide the simplest and most reliable disaster protection and site migration for all applications VMware vSphere VMware vCenter Server Site Recovery Manager VMware vCenter Server Site Recovery Manager VMware vSphere Site A (Primary)Site B (Recovery) Servers

9. 9 What’s New In Site Recovery Manager 5.0? Automated failback Planned migration Expand DR coverage to Tier 2 apps and smaller sites Streamline planned migrations (for disaster avoidance, planned maintenance, …) vSphere Replication Others  More granular control over VM startup order  Protection-side APIs  IPv6 support

10. 10 Key Components Of SRM 5 Storage Servers VMware vSphere vCenter Server Site Recovery Manager Virtual Machines Site Recovery Manager Manages recovery plans Automates failovers and failbacks Tightly integrated with vCenter and replication Storage-Based Replication (3 rd party) Provided by replication vendor Integrated via replication adapters created, certified and supported by replication vendor vSphere Replication Bundled with SRM Replicates virtual machines between vSphere clusters Choice of replication options Required at both protected and recovery sites

11. 11 SRM Provides Broad Choice of Replication Options vSphere Replication Simple, cost-efficient replication for Tier 2 applications and smaller sites Storage-based Replication High-performance replication for business-critical applications in larger sites vCenter Server Site Recovery Manager vSphere vCenter Server Site Recovery Manager vSphere vSphere Replication Storage-based replication Site A (Primary)Site B (Recovery)

12. 12 vSphere Replication Complements Storage-Based Replication

13. 13 Planned Migrations For App Consistency & No Data Loss Overview Benefits Two workflows can be applied to recovery plans:  DR failover  Planned migration Planned migration ensures application consistency and no data-loss during migration  Graceful shutdown of production VMs in application consistent state  Data sync to complete replication of VMs  Recover fully replicated VMs Better support for planned migrations  No loss of data during migration process  Recover ‘application-consistent’ VMs at recovery site Planned Migration Site B Site A Replication 1 Shut down production VMs 2 Sync data, stop replication and present LUNs to vSphere 3 Recover app- consistent VMs vSphere

14. 14 Simplify failback process  Automate replication management  Eliminate need to set up new recovery plan Streamline frequent bi-directional migarations Automated Failback To Streamline Bi-Directional Migrations Re-protect VMs from Site B to Site A  Reverse replication  Apply reverse resource mapping Automate failover from Site B to Site A  Reverse original recovery plan Restrictions  Does not apply if Site A has undergone major changes / been rebuilt  Not available with vSphere Replication Overview Benefits Automated Failback Site B Site A Reverse Replication Reverse original recovery plan vSphere

15. 15 Scalability MaximumEnforced Protected virtual machines total1000No Protected virtual machines in a single protection group 500No Protection groups150No Simultaneous running recovery plans10No vSphere Replicated virtual machines500No

16. 16 SRM Architecture

17. 17 SRM Architecture “Protected” Site“Recovery” Site VRMS vSphere Client SRM Plug-In vSphere Client SRM Plug-In VMFS Storage VMFS DB SRM Server DB vCenter Server ESX VMFS Storage VMFS ESX VRA VRS DB Replication

18. 18 Overall Solution Components vCenter – must be 5.0 and licensed and running on each site vSphere – must be 3.5 or later and running on each site SRM Server – Requires a Windows 64 bit OS. Storage Replication – must be on our compatibility list, and have the snapshot or clone technology licensed for SRM tests SRA – Storage Replication Adapter is the connection between VMware and the storage environment VRMS – vSphere Replication Management Server VRA – vSphere Replication Agent VRS – vSphere Replication Server ESXi 5.0 – Mandatory for vSphere Replication

19. 19 Storage Array Integration Storage Replication Adapters (SRAs):  Discover arrays  Determine which LUNs are replicated  Assist in initiating tests, recovery  New capabilities in SRAs for version 5.0 include ­Reprotect ­Synchronization ­Planned Migration SRM 5 will require new SRA’s SRM Compatibility Matrix:http://www.vmware.com/pdf/srm_storage_partners.pdfhttp://www.vmware.com/pdf/srm_storage_partners.pdf SRM Server SRA Vendor Management Interface Array Manager Replication Manager SRA Vendor Management Interface Array

20. 20 Storage Array Integration

21. 21 vSphere Replication

22. 22 ESXi Recovery SiteProtected Site ESX ESXi VSR Agent vSphere Replication Server Tightly Integrated With SRM, vCenter and ESX Site Recovery Manager vSphere Replication Management Server Any storage supported by vSphere vCenter Server vSphere Replication Architecture

23. 23 vSphere Replication Adding native replication to SRM Virtual machines can be replicated irrespective of underlying storage type Enables replication between heterogeneous datastores Replication is managed as a property of a virtual machine Efficient replication minimizes impact on VM workloads

24. 24 vSphere Replication Details  Replication options may be set per Virtual Machine Can opt to replicate all or a subset of the VM’s disks You can create the initial copy in any way you want - even via sneaker net! You have the option to place the replicated disks where you want. Disks are replicated in group consistent manner  Simplified Replication Management User selects destination location for target disks User selects Recovery Point Objective (RPO) User can supply initial copy to save on bandwidth  Replication Specifics Changes on the source disks are tracked by ESX Deltas are sent to the remote site Does not use VMware snapshots

25. 25 vSphere Replication UI Select VMs to replicate from within the vSphere client by right-click options Can configure for an individual VM, or multiple VMs simultaneously!

26. 26 vSphere Replication Components VR Agent Component of ESX host and ships with ESX Manages the replication process Schedules replications Transfers data to remote vSphere Replication servers Co-ordinates replication of VM configuration, and group consistency for VM disks Tracks changed blocks Replication traffic routed by VMkernel – not compressed or encrypted. VRMS ESX VRA DB

27. 27 vSphere Replication Components – continued vSphere Replication Server Linux virtual appliance at recovery side Deployed, configured, and managed by SRM Can scale by instantiating multiple servers Receives replication traffic from protection site Acts as a proxy, hiding details of the remote site from primary Writes incoming replication updates to VMDK files using ESX hosts Redo logs are used to preserve consistent updates Maintains 1 consistent instance per VM ESX VR Server DB VRMS

28. 28 vSphere Replication Components – continued vSphere Replication Management Server (VRMS) Generic management framework for vSphere Replication Orchestrates the creation of test and fail-over images One VRMS per VC Linux virtual appliance managed via the SRM UI Provides the vSphere Replication support to SRM Maps disks/VMs from primary site to directories / VMDKs at recovery site VRMS ESX VRA DB

29. 29 vSphere Replication 1.0 Limitations  Focus on virtual disks of powered-on VMs ISOs and floppy images are not replicated Powered-off/suspended VMs not replicated Non-critical files not replicated (e.g. logs, stats, swap, dumps)  VR works at the virtual device layer Independent of disk format specifics Independent of primary-side snapshots Snapshots work with VR, snapshot is replicated, but VM is recovered with collapsed snapshots Physical RDMs are not supported  FT, linked clones, VM templates are not supported with VR  Automated failback of VR-protected VMs will come later that the initial 5.0 release, but will be supported in the future.  Virtual Hardware 7 or later is required for VMs to be protected by VR.

30. 30 Simplify Replication Management With vSphere Replication Overview Benefits vSphere Replication provides simple management of replication  Managed directly from vCenter  Managed at the individual VM-level  Eliminate complex interactions between vSphere and storage teams to set up replication  Eliminate need to shuffle VMs between datastores to map applications to replicated LUNs Hub LUN 1 LUN 2 VMFS A Datastore Group Web SharePoint SQL App vSphere Replication Web SharePoint SQL App vSphere Admin Storage Admin vSphere Admin Storage-based Replication Datastore VMFS B Datastore

31. 31 User Interface  SRM’s interface is new and able to manage the entire SRM framework from one GUI. Both sides visible without Linked Mode!

32. 32 User Interface – Site-specific Networking settings for VMs New icons for shadow VMs

33. 33 SRM Use Cases

34. 34 Use Cases Recover from unexpected site failure Full or partial site failure The most critical but least frequent use-case Unexpected site failures do not happen often When they do, fast recovery is critical to the business Anticipate potential datacenter outages For example: in case of planned hurricane, floods, forced evacuation, etc. Initiate preventive failover for smooth migration Graceful shutdown of VMs at protected site Leverage SRM ‘planned migration’ capability to ensure no data-loss Most frequent SRM use case Planned datacenter maintenance Global load balancing Ensure smooth site migrations Test to minimize risk Execute partial failovers Use SRM planned migration to minimize data-loss Automated Failback enables bi-directional migrations Highly scalable 500 virtual machines File-system consistency with VSS Unplanned Failover Preventive Failover Planned Migration 3 typical

35. 35 Additional Use Cases – Upgrade, Patch Testing Storage Array Replication Protected SiteRecovery Site Test Replication – not impacted Isolated Test Network Copy of production

36. 36 Running DR Drills & Testing with SRM 5

37. 37 SRM Reduces Recovery Risk With Frequent Testing  During the testing gap, organizations can’t be sure that they can recover the current IT environment  A failover scenario may take days or weeks to complete, leaving the business at extreme risk SRM provides assurance that DR objectives will be met. Lack of confidence in DR process Time DR Test Changes to Applications and Infrastructure Configuration TESTING GAP Recovery Risk Traditional Disaster Recovery Recovery Risk DR Test Time Site Recovery Manager Frequent DR Testing

38. 38 Running a Test Recovery Plan API

39. 39 Testing a Recovery Plan – storage layer Storage Array Replication Protected SiteRecovery Site Replication – not impacted Isolated Test Network

40. 40 Testing a Recovery Plan

41. 41 Testing a Recovery Plan VM’s are ready to be used now

42. 42 Cleaning up a Test Recovery After testing is complete, the environment is easily cleaned up. Following cleanup, no test resources are in use at the recovery site Test or recovery is now ready to be run once again

43. 43 SRM Recovery & Planned Migration

44. 44 SRM Provides Broad Application Coverage Continuous Hours Days App-level geo-clustering / load balancing RTO RTO: 30 minutes to hours RPO: Flexible based on storage replication RPO SynchronousHoursDays Site Recovery Manager Tier 1 Apps Tier 2 Apps Tier 3 Apps

45. 45 SRM Supports Flexible Topologies Active-Passive Failover Active-Active Failover Bi-directional Failover Shared Recovery Sites Production Recovery Production Recovery Production Most common traditional scenario Expensive dedicated resources Leverage recovery infrastructure for test, development, training Utilize sunk cost of recovery site Production applications at both sites Each site acts as the recovery site for the other Many-to-one failover Particularly useful for Remote Office / Branch Office

46. 46 Application Consistent Recovery With SRM  Storage-based replication: application consistency widely available Enabled by replication management software Typically relies on agents in the VMs to properly quiesce applications For both DR failover and planned migrations  vSphere Replication: Application consistency for planned migrations only File-system consistency for DR failover via VSS requester in VMware Tools Application Consistency Enabled by Replication Provider Quiesce application Replicate app- consistent VM App-consistent VM presented to SRM Replication management

47. 47 Simple Setup And Management of Recovery And Migration Plans  Weeks or months to set up  Error-prone  Quickly falls out of sync with apps and infrastructure changes  Simple recovery plan set up in minutes  Fewer steps means far less room for errors  Simple to keep in sync with changes …to Simple Recovery PlansFrom Complex Runbooks…

48. 48 Step 2Step 3Step 4Step 5 Five Simple Steps To Create Recovery And Migration Plans Create Recovery Plans in 5 Steps… Step 1 Map production site resources to recovery site Resource pools vSwitches VM folders Select virtual machine protection groups to include in recovery Specify boot sequence of recovered VMs Customize IP addresses of recovered VMs Select low-priority VMs to suspend at recovery site …And Eliminate Manual Steps of Traditional Recovery Coordinate storage and replication processes for recovery Stop replication and make replicated LUNs writable Present data to applications Present VMs to vSphere Reconfigure individual hosts Reconfigure physical switching infrastructure Recover entire systems including OS and application binaries Add messages and custom scripts Optional

49. 49 Running a Recovery Plan API

50. 50 Planned Migration Will shutdown protected VM’s, and than synchronize them! Will stop on errors and let you fix them!

51. 51 Disaster Recovery Will shutdown protected VM’s, and than synchronize them IF it can! Will NOT stop on errors and let you fix them!

52. 52 Replication Running a Recovery Plan – Storage Layer Protected SiteRecovery Site

53. 53 Recovery The production workloads are now working on the recovery site.

54. 54 Failback  Failback is a use case that combines other SRM capabilities  Failback is a failover, a reprotect, and a subsequent failover  Process is shown started below with a successful planned migration.

55. 55 Failback - continued Replication now goes in reverse – to the protected side

56. 56 Failback - continued Following a reprotection, the environment may be “failed back” to the original primary site.

57. 57 History Reports Each workflow operation has an associated history report

58. 58 History Reports - continued

59. 59 SRM Advanced Settings

60. 60 Advanced – IP Customization The GUI shows IP customization for manual customization of IP addresses IP Customization information can now be configured for both protected and recovery sites Command line bulk IP customization includes support for both IPv6 addresses, and dual-site IP information No more Sysprep, or Customization Specifications required Performance of IP customization much faster

61. 61 Advanced – IP Customization – UI

62. 62 Advanced – IP Customization – command line Important to always pull down, and push up on the same side! This tool is found in the bin folder Dr-ip-customizer --cfg..\config\vmware-dr.xml -o c:\example.csv --cmd generate --vc vcenter-recovery Dr-ip-customizer --cfg..\config\vmware-dr.xml --csv c:\example.csv -- cmd apply --vc vcenter-recovery

63. 63 Advanced – VM Dependency Management SRM has 5 priority levels Within a priority group all virtual machines will start simultaneously

64. 64 Advanced – VM Dependency Management – continued Dependencies may be defined to dictate start sequence of VMs. This provides the ability to manage sophisticated start order of virtual machines so that it is easier to recover multi-tier apps.

65. 65 Advanced – VM Dependency Management – continued Database Apache Desktop Apache Mail SyncExchange App Server 2 Master Database App Server 1 Database

66. 66 Advanced – Scripts SRM 5 now supports in-guest scripts as well as the traditional script technology. Script that executes in VM context is executed under security of VMware Tools, Script that executes on SRM server is executed under security of SRM service credentials. Terminology of execution is the same between in-guest or SRM – for example: C:\windows\system32\cmd.exe /C “c:\scripts\call.cmd”

67. 67 Advanced – Scripts – continued

68. 68 SRM Edition & Licensing

69. 69 SRM 5 Editions Lineup SRM 5 StandardEnterprise Price per protected virtual machine (license only) $195$495 Scalability Limits Maximum protected VMs75 virtual machines (1) Unlimited (2) Features Support for storage-based replication Centralized recovery plans Non-disruptive testing Automated DR failover vSphere Replication Automated failback Planned migration New in SRM 5.0 1. Maximum of 75 VMs per site and per SRM instance 2. Subject to the product’s technical scalability limits

70. 70 Purchasing & Licensing Site Recovery Manager 5.0

71. © 2009 VMware Inc. All rights reserved Thank You