High Availability and Disaster Recovery Considerations for Hyper-V
-
Upload
arthur-voyager -
Category
Documents
-
view
226 -
download
0
Transcript of High Availability and Disaster Recovery Considerations for Hyper-V
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
1/43
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
2/43
igh Availability andisaster Recoveryonsiderations for Microsoft-yper V Bob Roudebush-Double Take Software
WSV311
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
3/43
Agenda
Hyper-V Virtualization ScenariosHow VM Availability, Disaster Recovery andBackup/Recovery Relate to BusinessContinuity
Anatomy of a Hyper-V Virtual MachineBackup/HA/DR for Hyper-V
Backup/Recovery Implications for Hyper-V VMs
High Availability Implications for Hyper-V VMs
Disaster Recovery Implications for Hyper-V VMs
Geo-Clustered Hyper-V VM Demonstration
Summary / Q&A
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
4/43
Hyper-V Virtualization
Scenarios
B u sin e ssB u sin e ssC o n tin u ityC o n tin u ity
D yn a m icD yn a m icD atacenterD atacenter
ServerServerC o n so lid a tio nC o n so lid a tio n
Test and DevTest and Dev
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
5/43
B u sin e ss C o n tin u ity,Resumption of full operations combining People Processes and
Platforms
Disaster Recovery- ,Site level crisis data and IT operations resumption
Backup and RestorePresumes infrastructure is whole
% /97 is file small unit related
High AvailabilityPresumes that the rest of the
environment is active
Keeping the Business Running
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
6/43
VHDHD haredStorage
/ackup Recovery
econdarySiterimarySite
torageArray torageArray
Virtualization reduces BC costs and minimizes businessVirtualization reduces BC costs and minimizes business increasing the availability of infrastructureincreasing the availability of infrastructure extending protection to more applicationsextending protection to more applications ,simplifying backups recovery and DR testing,simplifying backups recovery and DR testing
Business ContinuityBusiness Continuity
High AvailabilityHigh Availability
Disaster RecoveryDisaster Recovery
Backup and RecoveryBackup and Recovery
isaster Recovery
/ackup Recovery /ackup Recovery
ClusteringClustering
/Quick Live Migration/Quick Live Migration
Business Continuity
w/Virtualization
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
7/43
The Architecture of Hyper-V
Windows Server 2008
VSPWindows
Kernel
Applications Applications Applications
-Non Hypervisor Aware OS, Windows Server 2003 2008
WindowsKernel VSC
VMBus Emulation
Designed for Windows Server Hardware
Windows Hypervisor
-Xen Enabled Linux Kernel
Linux VSC
Hypercall Adapter
ParentPartition
Child Partitions
VM Service
WMIProvider
VMWorkerProcesses
UserMode
KernelMode
Ring-1
IHV Drivers
VMBus
VMBus
Applications
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
8/43
The Anatomy of a Hyper-V
VM . HD VM data. VHD VM snapshots*. IN Contents of VM RAMfor a saved state*. SV Saved state
( . .,information i e processor)register data
* . ML VM configurationinformation in an industry-
standard XML file
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
9/43
The Anatomy of a Hyper-V
VM
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
10/43
The Anatomy of a Hyper-V
VM
:ll VMs are assigned a unique GUID< =" ">logical_id type string 56B19F3FAD06C76416Dlogical_id ll snapshots are assigned a GUID used todentify the snapshot and construct. :elative paths to AVHDs< =" ">guid type string 3E0AC2C EE46C4F495D4guid( )oth the virtualized NIC s in the VM as well( )s the virtual switch es on the host are:ssigned a GUID< ChannelInstanceGuid
=" ">type string { }c66 ChannelInstanceGuid< =" ">SwitchName type string - - witch SM 847f89 SwitchName-ermissions related to Hyper VM are important:o consider< =" ">sid type string - - - 1 5 2 sid
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
11/43
VM Backup/Recovery
ChallengesExpense Loading Agents in EachGuest OSProtecting Virtualized Applications
(Exchange, SQL, etc.)VMs may Increase Backup/RestoreComplexity
Backing up in the guest Versus
outside the guest Image or file level recovery
Restoring to different hardware if
necessary
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
12/43
Some VM Backup
TerminologyFile-Level Backup In the GuestImage-Level Backup On the Host
Application Quiescing
O/S Crash ConsistencyApplication Crash Consistency
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
13/43
Types of VM Backups
Three types of BackupsBacking up the host system
May be necessary to maintain host configuration
But often, not completely necessary
The fastest fix for a broken host is often a completerebuild
Backing up Virtual Disk FilesFast and can be done from a single host-based backupclient
Challenging to do file-level restore
Backing up VMs from inside the VMSlower and requires backup clients in every VM.
Resource intensive on host
Capable of doing file-level restores
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
14/43
Challenges of Transactional
DBsO/S Crash Consistency is fairly easyQuiesce the NTFS file system beforebeginning the backup
Application Crash Consistency is muchharder
Tx databases like AD, Exchange and SQLdont quiesce just because NTFS does
Restoration without crash consistencywill lose data - DB restores intoinconsistent state and must performa soft recovery
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
15/43
Dealing with Consistency
When backing up VMs, may need to considerdual approaches: file level backups andimage-level backups
File-level = Restore Individual Files w/Tx Integrity
Image-level = Whole-Server RecoverabilityImage-level backups may not provide applicationcrash consistency!
MSFT and 3rd Party Solutions may integrate
with VSS-aware guest OS and applicationsMicrosoft System Center Data ProtectionManager
3rd Party Backup Solutions
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
16/43
Integrating Backup w/VSS
VSS = Volume Shadow CopyNo need to power down virtual machinesto do backups
VSS ensures a consistent state in the virtualmachine
Must have backup integration component enabled
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
17/43
Data Protection Manager2007Data Protection Manager 2007
Recovery Point Objective
15min versus RT for VSs-aware VMs
~1 day versus RT for non VSS-aware VMs
Recovery Time Objective
Automated Monitoring and Failover versuson-demand recovery
Type of Recovery Needed
Disaster Recovery focus on getting back
up and running with the latest copy ASAPOperational Recovery & Disaster Recovery focus on being able to recover multiplepoints in time
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
18/43
Secondary SitePrimary Site
-DPM for Hyper V-DPM for Hyper V -Live host level virtual machine backup In gue-Live host level virtual machine backup In gue
Bare metal restoreBare metal restore Rapid recovery Continuous Data ProtectionRapid recovery Continuous Data Protection No SAN requiredNo SAN required Protects VMsProtects VMs
( )without hibernation if OS is VSS enabled( )without hibernation if OS is VSS enabled
U p t o e v e r y 1 5 m i n u t e s
Microsoft Data ProtectionManager SP1
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
19/43
VSS/BackupRecommendations
VSS in Hyper-V does not support:Host-level backups of pass-through VHDs.
Host-level backups of iSCSI volumes in guest VMs
Instead, use guest-based Exchange-aware
streaming backup or VSS backupData Protection Manager 2007
VSS in Hyper-V does support host-levelbackups of VHDs
Hardware-based VSS backups of ExchangeStorage
Supported by the vendor, not Microsoft
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
20/43
Hyper-V Backup BestPracticesEnsure your backup solution supportsVSS
Support for the VSS writer in Hyper-Vspecifically
Virtual Machine Backup Best practicesLeverage the Hyper-V VSS writer to takeonline snapshots of virtual machines
System Center Data Protection Managerwill provide Hyper-V VSS snapshots
Ability to quickly recover virtualmachines
Replicate snapshots to backup location
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
21/43
Virtualization & HighAvailability
- dition alN on V irtualized Environm ent-dition alN on V irtualized Environm ent,n tim e is b a d b u t a ffe cts o n ly o n e w orklo a d,tim e is b a d b u t a ffe cts o n ly o n e w o rklo a d
V irtualized Environm entV irtualized Environ m ent Va lu e o f th e p h ysical serve rVa lu e o f th e p h ysical serve r
g o e s u pg o e s u p D ow n tim e is fa r w o rse b e ca u se m u ltip le w o rklo a d s aD ow n tim e is fa r w o rse b e ca u se m u ltip le w o rklo a d s a
-irtualization and High Availability Go Hand-irtualization and High Availability Go Handn Handn Hand
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
22/43
Microsoft Hyper-V QuickMigration
Provides solutions for both planned andunplanned downtime
Planned downtimeQuickly move virtualized workloads to service
underlying hardwareMore common than unplanned
Unplanned downtimeAutomatic failover to other nodes
(hardware or power failure)Not as common and more difficult
Windows Server 2008 R2 introduces Live-migration supporting movement ofvirtual machines between servers with no loss of service
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
23/43
Quick MigrationFundamentalsSave state
Save entire virtualmachine state
Move virtual
machineMove storageconnectivity fromorigin to
destination hostRestore state andrun
Restore virtual
machine
etwork Connectivityetwork Connectivity
hared Storagehared StorageVHDsHDs
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
24/43
Other VM AvailabilityScenarios
Guest-based VM clustering (using WSFC)Cost prohibitive requires Enterprise edition ofWindows Server and shared storage
More complex to install/configure/manage
An option for cluster-aware applications3rd party replication/failover solutions
Use software-based replication/failover toreplicate VMs between Hyper-V hosts (or withinVMs)
Double-Take for Hyper-V
CA XOsoft High Availability
SteelEye LifeKeeper for Windows
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
25/43
Disaster RecoveryChallengesDowntime is Expensive
Traditional DR is slow/complex
Increased pressed on IT foravailability
Requires specialized training
T h in g s a re C o m p lica te d
/Tra d itio n a lD R re q u ire s id e n tica l H W S Wco n fig s
-D ifficu lt to te st m u lti tie r a p p lica tio n s
/In fra stru ctu re Pe o p le a reE xp e n sive
D u p lica te d a ta ce n te rin fra stru ctu re s
S ig n ifica n t p e rso n n e l re so u rce sre q u ire d
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
26/43
Virtualization Benefits
Downtime is ExpensiveMore Rapid Backup and Recovery
Quick/Live Migration/Clustering
Requires specialized training
T h in g s a re C o m p lica te d
E lim in a te m a in ta in in g d u p lica te p h ysica lsystem s
,A u to m a te B a c ku p R e c o v e ry a n d D Rprocesses
/In fra stru ctu re Pe o p le a re E xp e n siveR e d u ce e xp e n d itu re o n fa cility a n d
in fra stru ctu re
D im in ish n e e d fo r sp e cia lize d/h ard w are p e rson n el
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
27/43
Some DR Terminology
RTO Recovery Time ObjectiveHow much data you can afford to lose
RPO Recovery Point ObjectiveHow long you can afford to be down
Hot siteServers up and operational at remote site at alltimes.
Warm site
Servers pre-provisioned at remote site. Tasks tocomplete for failover to occur.
Cold siteEmpty site and servers on retainer awaiting DR
event.
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
28/43
Hyper-V Recovery "ValueMeals"
Recovery TimeObjective Recovery PointObjective What should I use itfor?
Small >1 Day to Week(s) > 1 Day to Week(s) Development andTesting Systems
Medium > 4 Hours to Day(s) > 4 Hours to Day(s) Workgroup
Applications
Large Minutes to Hour(s) Minutes to Hour(s) Infrastructure Systemsand MessagingSystems
Biggie Size Immediate Real-Time Business-Critical
Systems$$$$$$$
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
29/43
Days to Weeks Recovery
Use free or low-cost solutions to backup VMsat the host level (image-level backups)
DR site is a cold site with equipmentavailable
on-demand from a vendor/co-lo companyStore images to tape/disk and rotate off-site
Will need to manually restore imagesand fix problems .
and there will be problems!
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
30/43
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
31/43
Minutes to Hours Recovery
Use replication to provide site-to sitereplicationof VM data
These host-level replicated VM copies
are potentially inconsistentCan use SAN-based or host-based replicationCost / Bandwidth trade-off
Less impact to WAN changes being sent in
real-time (compression/throttling)Will need to attach replicated VMs toreplacement equipment and fix problems
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
32/43
Immediate Recovery
Warm or hot site is used for DRStorage to storage replication installedbetween sites
3rd party replication technologies used
for VM replicationin the guest for transactional integrity
on the host for all other workloads
Restoration is usually automated using
3rd party tools or interoperability withWindows Server Failover Clustering
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
33/43
Windows Server 2008 -WSFCNo More Single-Subnet Limitation
Allows cluster nodes to communicateacross network routers
No more having to connect nodes with
VLANs!Configurable Heartbeat Timeouts
Increase to extend geographically
dispersed clusters over greater distancesStorage Vendor Based SolutionMirrored storage between stretchedlocations
Hardware or Software based replication
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
34/43
GeoCluster
Integrates with Microsoft Failover ClusteringUses Double-Take Patented Replication
Extends Clusters Across GeographicalDistances
Eliminates Single Point of Disk Failure
GeoCluster for Hyper-V WorkloadsUtilizes GeoCluster technology to extend Hyper-Vclustering across virtual hosts without the use ofshared disk
Allows manual and automatic moves of clusterresources between virtual hosts
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
35/43
G e o C lu ste r n o d e s u se sep a ra te, -d isks kep t syn ch ro n ized b y re a l
tim e re p lica tio n
Only theactive nodeaccesses its
disks
,At failoverthe new activenode resumes
,with currentreplicated
data
Data is replicatedto all passive
nodesReplicatio
n
How GC Integrates w/WSFC
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
36/43
-Multi site stretch configurations can-Multi site stretch configurations can- provide automatic fail over- provide automatic fail over
econdary Siteecondary Siterimary Siterimary Site
SANAN SA NANeplicated data from site A
toragetorageArrayrray toragetorageArrayrray
Geographically distributed clusters are extendGeographically distributed clusters are extendto differentto different
physical locationsphysical locations Stretch clustering uses the same concept as loStretch clustering uses the same concept as lo
site clusteringsite clustering Storage array or third party software providesStorage array or third party software provides
ch Clustering automatically fails VMs over to a geographically different site
rimary site data is replicated to the secondary site
Microsoft Stretch Clustering& Storage Continuity
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
37/43
-Software based Quick/ -Migration Geo clustering for
-Hyper V VMs
emo
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
38/43
. . /www microsoft com teched
- &Sessions On Demand Community
:// . /http microsoft com technetResources for IT Professionals
:// . /http microsoft com msdnResources for Developers
. . /www microsoft com learningMicrosoft Certification and Training
Resources
. . /www microsoft com learning
&Microsoft Certification TrainingResources
Resourcesn .ne
http://www.microsoft.com/techedhttp://www.microsoft.com/techedhttp://microsoft.com/technethttp://microsoft.com/technethttp://microsoft.com/msdnhttp://microsoft.com/msdnhttp://www.microsoft.com/learninghttp://www.microsoft.com/learninghttp://www.microsoft.com/learninghttp://www.microsoft.com/learninghttp://www.microsoft.com/learninghttp://www.microsoft.com/learninghttp://microsoft.com/msdnhttp://microsoft.com/technethttp://www.microsoft.com/teched -
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
39/43
( )nteractive Theater Sessions session codes and titles( )nteractive Theater Sessions session codes and titles- :V IR 0 4 IN T W h y V irtu a liza ito n a n d D a ta Pro te ctio n a re B e tte r- :V IR 0 4 IN T W h y V irtu a liza ito n a n d D a ta Pro te ctio n a re B e tte r
TogetherTogether
R elated C on ten t( )reakout Sessions session codes and titles( )reakout Sessions session codes and titles: .V IR 3 1 1 Fro m Z e ro to Live M ig ra tio n H o w to S e t U p a Live: .V IR 3 1 1 Fro m Z e ro to Live M ig ra tio n H o w to S e t U p a Live
M ig ra tio nM ig ra tio n
: W S V 2 0 2 C o n sid e ra tio n s an d S tra te g ie s fo r D e p lo yin g V irtu a l: W S V 2 0 2 C o n sid e ra tio n s an d S tra te g ie s fo r D e p lo yin g V irtu a lC lu ste rsC lu ste rs
: W S V 3 1 3 In n o v a tin g H ig h A v a ila b ility w ith C lu ste r S h a re d: W S V 3 1 3 In n o v a tin g H ig h A v a ila b ility w ith C lu ste r S h a re dVV oo lu m e slu m e s
: - ( ) W S V 3 1 5 Im p le m e n tin g H yp e r V o n C lu ste rs H ig h A va ila b ility: - ( ) W S V 3 1 5 Im p le m e n tin g H yp e r V o n C lu ste rs H ig h A va ila b ility
: :W S V 3 2 8 W in d o w s S e rv e r 2 0 0 8 R 2 H y p e rV: :W S V 3 2 8 W in d o w s S e rv e r 2 0 0 8 R 2 H y p e rV
- ( )ands on Labs session codes and titles( )ands on Labs session codes and titlesV IR 0 4V IR 0 4 : -HOL Introduction to Hyper V: -HOL Introduction to Hyper V
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
40/43
Windows Server Resources Make sure you pick upMake sure you pick up
your copy of Windowsyour copy of WindowsServer 2008 R2 RC fromServer 2008 R2 RC from
the Materialsthe MaterialsDistribution CounterDistribution Counter
:Learn More about Windows Server 2008 R2:Learn More about Windows Server 2008 R2 . . /www microsoft com WindowsServer2008R2. . /www microsoft com WindowsServer2008R2
(Technical Learning Center Orange(Technical Learning Center Orange):Section):Section
Highlighting Windows Server 2008 and R2 technologiesHighlighting Windows Server 2008 and R2 technologies Over 15 booths and experts from Microsoft and ourOver 15 booths and experts from Microsoft and our
partnerspartners
http://www.microsoft.com/WindowsServer2008R2http://www.microsoft.com/WindowsServer2008R2http://www.microsoft.com/WindowsServer2008R2http://www.microsoft.com/WindowsServer2008R2http://www.microsoft.com/WindowsServer2008R2 -
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
41/43
valuation on CommNet and enter to win!valuation on CommNet and enter to win!
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
42/43
&uestionanswer
-
8/7/2019 High Availability and Disaster Recovery Considerations for Hyper-V
43/43
. . , , / . . / 2009 Microsoft Corporation All rights reserved Microsoft Windows Windows Vista and other product names are or may be registered trademarks and or trademarks in the U S and or other.countries
.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation Because Microsoft must respond, ,to changing market conditions it should not be interpreted to be a commitment on the part of Microsoft and Microsoft cannot guarantee the accuracy of any information provided after
. , , , .the date of this presentation MICROSOFT MAKES NO WARRANTIES EXPRESS IMPLIED OR STATUTORY AS TO THE INFORMATION IN THIS PRESENTATION