vmware virtualization for business continuity and disaster recovery
DESCRIPTION
VMware Virtualization for Business Continuity and Disaster Recovery. David Lefebvre Sr. Systems Engineer. Agenda. Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery vSphere + Replication Site Recovery Manager Metro Clustering. 2. - PowerPoint PPT PresentationTRANSCRIPT
© 2009 VMware Inc. All rights reserved
VMware Virtualization for Business Continuity and Disaster Recovery
David Lefebvre
Sr. Systems Engineer
2 Confidential2
Agenda Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery
vSphere + Replication Site Recovery Manager Metro Clustering
3 Confidential
43% of companies experiencing disasters never re-open,
and 29% close within two years(McGladrey and Pullen)
93% of business that lost their data center for 10 dayswent bankrupt within one year(National Archives & Records Administration)
40% of all companies that experience a major disasterwill go out of business if they cannot gain accessto their data within 24 hours(Gartner)
Top executives say 10 hours to recovery;IT managers say up to 30 hours (Harris Interactive)
Disasters Happen. Do You Need Protection?
Business-Critical Services Require Business Continuity
38%
43%53%
25% 25%
MS Exchange
MS SQLMS SharePoint
OracleMiddleware
OracleDB
XenApp
42%
SAP
18%
Source: VMware customer survey, January 2010, sample size 1038Data: Total number of instances of that workload deployed in your organization and the percentage of those instances that are virtualized
44
% of Application Instances running on VMware in Customer Base
Availability expectations continue to increase• RTO’s decreasing from >24 hours to <12 hours
DataProtection
DisasterRecovery
LocalAvailability
Traditional Availability Silos Are Complex and Expensive
App Server Clusters
Session State Replication
Middleware / Java
DB Access Group
CCR / SCR
DB Mirroring
MS Clustering
Oracle RAC
Oracle DataGuard
Custom solution for each application stackComplex and expensiveHighly skilled staff to configure and manageRisk of errorsExpensive licenses (e.g. RAC)Dedicated standby infrastructure
5
Business Continuity As An Infrastructure Service For All Apps
Resource Pool
vSphere vSphere vSphere
Local Site Failover Site
• vCenter Site Recovery Manager
• MetroClustering
• VMware High Availability (app-aware)• VMware Fault Tolerance• VMotion
• VMware Data Recovery• vStorage APIs for Data Protection
Resource Pool
vSphere vSphere
Dev /Test
Dev /Test
Dev /Test
Disaster RecoveryLocal Availability
Data Protection
6
• Application and OS independent • Focus on simplicity, cost-efficiency
Copyright © 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
BC/DR is the #1 reason why people virtualize …
Top Five Objectives for Virtualization
Use virtualization to improve Business Continuity and Disaster Recovery (BCDR) 46%
Improve virtual machine performance 33%
Increase the server consolidation ratio 32%
Improve VM environment management 31%
More mission-critical applications 24%
Source: WW VMware customer survey, January 2010N=1083
8Copyright © 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Local Availability Disaster Recovery
VMware Business Continuity Pillars
Data Protection
X
Reliable Platform
9Copyright © 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Rock-Solid Platform Is The Foundation
Protection against component failures• NIC teaming• Storage multipathing
ESX stability• End-user system with >
3 years continuous uptime
“This is the ‘accidentally built a wall around it and forgot it was there’ kind of reliable. The
code is virtually bomb-proof.”
- Redmond Magazine - Editor’s Choice Awards
10 Confidential10
Agenda Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery
vSphere + Replication Site Recovery Manager Metro Clutering
11 Confidential
vStorage APIs for Data Protection
Traditional backup• Disruptive to applications and users• Slow, complex process for full restore• Hardware dependencies complicate
restore
Backup with VMware vSphere• Non-disruptive to applications & users• Enables off-host, off-LAN backup with
standard backup software via vStorage APIs for Data Protection
• Enables image and file-level backup of virtual machines
• VSS quiescing for app consistency (OS level consistency in Windows 2008)
VMware enables scalable, non-disruptive backup and simple, reliable restore to any hardware
VM Snapshot
OSAPP
ESXOS
APPOS
BACKUP APP
Backup Job
OSAPP
Tape or disk
Backup Partner Solutions
ArcServe NetBackup & Backup Exec
vRanger
Tivoli Storage Manager
AvamarSimpana
12 Confidential
VirtualCenter
VirtualCenter
VMware Data Recovery – New in vSphere 4!
• Agent-less, disk-based backup and recovery of your VMs
• VM or file level restore
• Incremental backups and data de-dupe to save disk space
• Quick, simple and complete data protection for your VMs
• Centralized Management through VMware Infrastructure client
• Cost-effective use of storage for backup data
1. Backup
2. Restore
1.VM goes down2.Select VM images/files
to recover3.Restore…VM running
in seconds
X
1.Schedule backups via VC2.Snapshots taken3.Data de-duped and stored
vCenter Server
X
De-duplicatedStorage
vCenter Server
19
Agenda Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery
vSphere + Replication Site Recovery Manager Metro Clustering
20 Confidential
Challenges of Traditional Disaster Recovery
Complex recovery requirements
Dependent on manual
processes, perfect training, documentation, and execution
Failure to meet business objectives
• Expensive
• Days or weeks to recover
• Unreliable – manual untested processes and configuration drift
??
?
??
??
?
21 Confidential
Key Features of Virtualization for Disaster Recovery
Encapsulation• All information about a system is stored as data on disk• Entire systems can be protected with data protection tools
Hardware-Independence• Reliably recover a virtual machine to any hardware• Enable waterfalling of equipment to recovery site
Consolidation• Reduced hardware requirements at production and DR site• Can use higher consolidation ratios at DR site
22 Confidential
Simplifying the Disaster Recovery Process
Eliminate recovery steps• No operating system re-install or bare-metal recovery• No time spent reconfiguring hardware
Standardize recovery process• Consistent process independent of operating system
and hardware
Configure hardware
Install OS
Configure OS
Install backup agent
Start “Single-step automatic recovery”
RestoreVM
Poweron VM
Physical
Virtual 40+ hrs < 4 hrs
23 Confidential
Storage
Servers
VMware vSphere
Virtual Machines
vSphere + 3rd Party Replication Provides Robust DR Foundation
Storage
Servers
VMware vSphere
Virtual MachinesActive Site Failover Site
Host-BasedReplication
StorageReplication
• Encapsulation provides simple one-step replication for OS, app, and data• Hardware independence reduces hardware requirements and risks at failover site• Consolidation reduces DR costs• 3rd party replication can be “Storage Replication” or “Host-Based Replication”
• Provided by 3rd party today (HBR provided by VMware in future)• SRM requires “Storage Replication” today (HBR support in future)
• Application-consistency can be ensured by replication provider
24
Agenda Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery
vSphere + Replication Site Recovery Manager Metro Clustering
25 Confidential
vCenter Site Recovery Manager Automates DR
• Automates recovery workflows Manual runbooks captured in
automated recovery plans
• Ensures fast, predictable RTO Minutes to hours
• Enables non-disruptive testing of recovery plans• Provides central management from
the VMware vSphere Client
Works with VMware vSphere to make disaster recovery rapid, reliable,
manageable, affordable
Site Recovery Manager leverages VMware vSphere to deliver advanced disaster recovery management and automation
26 Confidential
SRM Momentum
Introduced in Q2’ 2008100,000+ units sold3,000+ customers
50% annual growth in 2010
“If your organization is already taking advantage of virtualization, then adding Site Recovery Manager to handle disaster recovery is a no-brainer.”
― Jerry Wilkin Senior Systems Administrator, Dayton Superior Corp
27 Confidential
SRM Today: Key Components
Storage
Servers
VMware vSphere
vCenter ServerSite
Recovery Manager
Storage
Servers
VMware vSphere
Virtual Machines
vCenter ServerSite
Recovery Manager
Virtual Machines
Site Recovery Manager• Manages and monitors recovery plans• Tightly integrated with vCenter Server
VMware vSphere• Requires supported version of ESX• Requires supported version of vCenter Server
Storage• iSCSI, FibreChannel or NFS storage
Storage Partner Replication• Integrated via replication adapters created,
certified and supported by replication vendor
Partner Replication
28 Confidential
SRM Complements vSphere + Replication
Traditional DR
vSphere + 3rd Party Replication
SRM + vSphere + Replication
Encapsulation for simple replication of OS + App + data XHardware independence at failover site XConsolidation to reduce costs XSimple recovery of individual machines (OS + App + data) X Automated runbooks / workflows X XFast, reliable RTO X XNon-disruptive testing X XCentralized DR management X X
(1) Simple with Host-Based Replication, requires scripting with Storage Replication
(1)
29 Confidential
SRM Futures
From SRM to“Site Manager”
EnhancedFunctionality
OSAPP
OSAPP
OSAPP
Long-DistancevMotion
Host-BasedReplication
DR to theCloud
SRM = Site Manager
• Automated failback• Enhanced scalability• More control over VM startup order• Application consistency for planned migrations• More flexible integration with broader set of 3rd party
products
30 Confidential
SRM Covers Broad Range Of Apps
Minutes
Hours
Days
# Applications
Tier I
Tier II
Tier III
Tier IV
Geo-clustering, distributed applications
Server-based replicationBackup / restore
Site Recovery Manager
RTO
RTO: 10 minutes to hoursRPO: Flexible based on storage replication
31 Confidential
SRM Reduces Recovery Risk
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
Virtualization & DR Automation Greatly Reduce Recovery Risk
Unproven Recoverability
TimeDR Test DR Test
Changes to Applications &
Infrastructure Configuration
TESTING GAP
RecoveryRisk
IT Environment withoutVirtualization & DR Automation
RecoveryRisk
DR Test DR Test
Frequent DR Testing
Time
Virtualization + DR Automation
Virtualization
32 Confidential
Disaster Recovery Scenarios with Site Recovery Manager
Active-PassiveFailover
Active-ActiveFailover
Bi-directional Failover “Local” Failover
Production
Recovery
Production
Recovery
Production
Production
Production
• Most common traditional scenario
• Very expensive architecture
• Leverage recovery infrastructure for test, development, training
• Reduces sunk cost of recovery site
• Production applications at both sites
• Each site acts as the recovery site for the other
• Less common scenario
• Protection against large localized failures in datacenter
33 Confidential
Deployment Topologies
Standard Deployment• 1:1 mapping between each
protected site and its recovery site
Shared Recovery Sites• Multiple sites can be protected by
a single, shared recovery site• Leverage for remote office/branch
office topologies
34 Confidential
Disaster Recovery Setup
Integrate with replication• Identify which virtual machines are
protected by replication configuration
Map recovery resources• Server resources, network resources,
management objects
Create recovery plans • For virtual machines, applications,
business units• Convert manual runbook to
pre-programmed response• Customizable with scripting and callouts
• Simplify configuration of recovery infrastructure and process• Simplify coordination of replication with virtual environment
Site A Site B
Replication
35 Confidential
Setting Up Protection Groups Requires Careful Planning
Datastore Group 1
LUN 1
Protection Group 1Exchange
DatastoreVMFS A
LUN 4
LUN 5
VMFS C
VMFS D
Datastore Group 2
Datastore
Datastore
CAS Hub Mailbox
Web
Protection Group 2SharePoint
SQL
App/OS
DB/log
Protection Group 1
Recovery Plan 1 (Exchange only)
Protection Group 1
Recovery Plan 2 (Exchange and SharePoint)
Protection Group 2
Key considerations for setting up LUNs and Protection Groups• Granularity of protection groups – Smallest number of apps to recover at once?• Application dependencies – which VMs are required for full application recovery?• Consistency groups – which VM disks need to be replicated on consistent schedule?• Application consistency – is a separate LUN required for the data, for example to
support 3rd party ‘application consistent’ replication?
36 Confidential
Creating and Editing Recovery Plans
Recovery plan editor
37 Confidential
Testing
Create isolated test environment• Snapshot replicated LUNs before test• Change all virtual machines to a test port
group before powering them on
Automate test execution• Using recovery plan created during setup• Customizable for testing with extra
breakpoints and callouts for test• Log test execution
Reset environment after test• Power off and delete any test VMs• Delete snapshots of replicated LUNs
• Non-disruptive testing of recovery plans• Testing can incorporate existing/non-virtual DR tools and processes
Site B
38 Confidential
Testing and Executing Recovery Plans
Steps in recovery plan Status and time
stamps
When to execute
User confirmation
message
39 Confidential
Site BSite A
Replication
Failover Automation
Detect site failures• Raise alert when heartbeat lost
Initiate failover• User confirmation of outage• Granular failover initiation
Manage replication failover Break replication Make replica visible to recovery hosts
Execute recovery process• Use pre-programmed plan• Provide visibility into progress
• Automation for failover process• Real-time, step-by-step visibility into execution progress
40 Confidential
Site B
Failback
Configuring failback• Original site is again operational• Set up replication in reverse• Reconfigure SRM so that the original
site is now the recovery site• Create new recovery plan for failback
Executing failback• Test and execute automated failback
with Site Recovery Manager to restore operation at original site
Restoring protection• Configure replication so that protected
VMs are replicated to recovery site• Recreate and test recovery plans
Controlled and automated failback using SRM
Site A
Original Site Recovery Site
Reverse ReplicationReplication
41 Confidential
Using SRM for Datacenter Migrations
Current Site New Site
Replication
Map Application Dependencies• Understand what needs to “move
together” (applications + data)
Create one or more migration plans• Specify which VMs are part of each
migration• Ensure storage replication is set up to
copy the right data set for each move• Best to migrate in multiple phases to
keep downtime to a minimum
Test migration plans before executing• Ensure correct & complete migration for
each group of VMs• Bring the apps up at the new site in a test
bubble to check the application layer
Automated execution of migration
42Copyright © 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Purchasing & Licensing Site Recovery Manager 4.1
• Requires vCenter Server 4.1
• Works with ESX 3.x and 4.x Not compatible with vSphere
Essentials packages
Site Recovery Manager 4
vSphereEnterprise Plus,
Enterprise,Advanced, or
Standard
vCenter Server 4Standard or Foundation
VMware Infrastructure 3Enterprise,Standard,
Foundationand/or
Separate Purchase from VMware vSphere
License required for each protected Virtual Machine or server
1 instance required at each site
Licenses required for servers at both sites
• Available a la carte or via product bundles
• SRM licenses are purchased for servers running protected VMs
• Sold “Per VM” or “Per Proc” (“Per proc” only until 12/15)
DO NOT DISTRIBUTE TO ANY PERSONS OUTSIDE OF VMWARE, INC.
“Per VM” Pricing Is Better Aligned With SRM Use Cases
Before• Fragment compute resources to
create dedicated “SRM cluster”
• Pay for all VMs on “SRM cluster”, including unprotected VMs
After• Single cluster, no resource
fragmentation
• Pay only for protected VMs
• Flexible ‘pay per use’, cost directly related to utilization
Protected VMs
Non-SRM Cluster SRM Cluster
Single Cluster
Protected VMs
DO NOT DISTRIBUTE TO ANY PERSONS OUTSIDE OF VMWARE, INC.44
Agenda Introduction – VMware for Business Continuity Data Protection Local Availability Disaster Recovery
vSphere + Replication Site Recovery Manager Metro Clustering
DO NOT DISTRIBUTE TO ANY PERSONS OUTSIDE OF VMWARE, INC.
Metro Clustering – Short-Distance Stretched vSphere Cluster
Active-Active Storage Cluster
Site A Site BStretched vSphere Cluster
Max 100 km
• Behaves just like a single vSphere cluster• Stretched across two sites max 100km apart, typically <20km• Automated DR protection / avoidance through VMware HA and vMotion• Requires active-active storage cluster, for example EMC VPLEX or NetApp MetroCluster
47 Confidential
Next Steps
48 Confidential
Successful Business Continuity Requires Careful Planning
Business Requirements / Business Impact Analysis (BIA)• Map service Tiers by availability requirements and cost• For each service, identify Availability requirements, Recovery Time Objectives
(RTO), Recovery Point Objectives (RPO)
Application Dependency Mapping• Identify dependencies between application components• Weakest link in the chain? (AD, DNS, etc)
Business Continuity Design• App-specific solutions / virtualization for HA and DR / backup only• Budget ahead of time• Project planning / phasing
Use Professional Services• VMware PSO• VMware BCDR Competency partners (300+ highly qualified partners)
49 Confidential
VMware BC/DR Service Offerings
VMware vCenter Site Recovery Manager Jumpstart• The VMware vCenter Site Recovery Manager Jumpstart provides you
with a proof-of-concept, on-site installation and configuration of SRM
• 3 days on-site, 5 participants max
Plan and Design for VMware vCenter Site Recovery Manager• The Plan and Design for VMware vCenter Site Recovery Manager service
provides a comprehensive architectural design for SRM that addresses your requirements, accommodates VMware vSphere dependencies
• Offered in 3-tiers as a soft-bundle
50 Confidential
Where Can I Learn More?
vCenter Site Recovery ManagerProduct Page – www.vmware.com/products/srm
Overview, datasheet, webinars, docs, community linksFree 60-day Evaluation – all you need to get started!
Business Continuity Solutions from VMware – www.vmware.com/solutions/continuityVMbook on BC/DR – www.vmware.com/resources/techresources/1063
External Resources Administering VMware Site Recovery Manager book by Mike Laverick – http://www.lulu.com/content/4343147
© 2009 VMware Inc. All rights reserved
Questions?