High Availability  and Disaster Recovery  Considerations for Microsoft Hyper-V<br />Ing. Eduardo Castro, PhD<br />Grupo As...
Agenda<br />Hyper-V Virtualization Scenarios<br />How VM Availability, Disaster Recovery and Backup/Recovery Relate to Bus...
Hyper-V Virtualization Scenarios<br />Business Continuity<br />Server Consolidation<br />Test and Dev<br />Dynamic Datacen...
Business Continuity<br />Resumption of full  operations combining People, Processes  and Platforms<br />Disaster Recovery<...
Business Continuity w/Virtualization<br />Business Continuity<br />Virtualization reduces BC costs and minimizes business ...
extending protection to more applications
simplifying backups, recovery and DR testing</li></ul>Primary Site<br />Secondary Site<br />High Availability<br />Disaste...
The Architecture of Hyper-V<br />VMWorkerProcesses<br />Parent Partition<br />Child Partitions<br />Applications<br />Appl...
The Anatomy of a Hyper-V VM<br />.VHD – VM data<br />.AVHD – VM snapshots<br />*.BIN – Contents of VM RAM for a saved stat...
The Anatomy of a Hyper-V VM<br />
The Anatomy of a Hyper-V VM<br />All VMs are assigned a unique GUID:<br />&lt;logical_id type=&quot;string&quot;&gt;056B19...
VM Backup/Recovery Challenges<br />Expense – Loading Agents in Each Guest OS<br />Protecting Virtualized Applications (Exc...
Some VM Backup Terminology<br />File-Level Backup – “In the Guest”<br />Image-Level Backup – “On the Host”<br />Applicatio...
Types of VM Backups<br />Three types of Backups<br />Backing up the host system<br />May be necessary to maintain host con...
Challenges of Transactional DBs<br />O/S Crash Consistency is fairly easy<br />Quiesce the NTFS file system before beginni...
Dealing with Consistency<br />When backing up VMs, may need to consider dual approaches: file level backups and image-leve...
Integrating Backup w/VSS<br />VSS = Volume Shadow Copy<br />No need to power down virtual machines to do backups<br />VSS ...
Data Protection Manager 2007<br />Data Protection Manager 2007<br />Recovery Point Objective<br />15min versus RT for VSs-...
Microsoft Data Protection Manager SP1<br /><ul><li>DPM for Hyper-V
Live host-level virtual machine backup In guest consistency
Bare metal restore
Rapid recovery Continuous Data Protection
No SAN required
Protects VMs without hibernation (if OS is VSS enabled)</li></ul>Secondary Site<br />Primary Site<br />Recovery<br />Up to...
VSS/Backup Recommendations<br />VSS in Hyper-V does not support:<br />Host-level backups of pass-through VHDs.<br />Host-l...
Hyper-V Backup Best Practices<br />Ensure your backup solution supports VSS<br />Support for the VSS writer in Hyper-V spe...
Virtualization & High Availability<br />Traditional Non-Virtualized Environment<br /><ul><li>Downtime is bad, but affects ...
Downtime is far worse because multiple workloads are affected</li></ul>Virtualization and High-Availability Go Hand in Han...
Microsoft Hyper-V Quick Migration<br />Provides solutions for both planned and unplanned downtime<br />Planned downtime<br...
Quick Migration Fundamentals<br />Save state<br />Save entire virtual machine state<br />Move virtual machine<br />Move st...
Other VM Availability Scenarios<br />Guest-based VM clustering (using WSFC)<br />Cost prohibitive – requires Enterprise ed...
Virtualization Benefits<br />Downtime is Expensive<br />More Rapid Backup and Recovery<br />Quick/Live Migration/Clusterin...
Some DR Terminology<br />RTO – Recovery Time Objective<br />How much data you can afford to lose…<br />RPO – Recovery Poin...
Hyper-V Recovery &quot;Value Meals&quot;<br />$$$$<br />
Days to Weeks Recovery<br />Use free or low-cost solutions to backup VMs at the host level (image-level backups)<br />DR s...
Upcoming SlideShare
Loading in …5
×

Hyper V High Availabitiy

2,611 views

Published on

Ing. Eduardo Castro, PhD
http://comunidadwindows.org
http://mswindowscr.org

Published in: Business, Technology
0 Comments
9 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,611
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
9
Embeds 0
No embeds

No notes for slide

Hyper V High Availabitiy

  1. 1. High Availability and Disaster Recovery Considerations for Microsoft Hyper-V<br />Ing. Eduardo Castro, PhD<br />Grupo Asesor en Informática<br />ecastro@grupoasesor.net<br />
  2. 2. Agenda<br />Hyper-V Virtualization Scenarios<br />How VM Availability, Disaster Recovery and Backup/Recovery Relate to Business Continuity<br />Anatomy of a Hyper-V Virtual Machine<br />Backup/HA/DR for Hyper-V<br />Backup/Recovery Implications for Hyper-V VMs<br />High Availability Implications for Hyper-V VMs<br />Disaster Recovery Implications for Hyper-V VMs<br />Geo-Clustered Hyper-V VM Demonstration<br />Summary / Q&A<br />
  3. 3. Hyper-V Virtualization Scenarios<br />Business Continuity<br />Server Consolidation<br />Test and Dev<br />Dynamic Datacenter<br />
  4. 4. Business Continuity<br />Resumption of full operations combining People, Processes and Platforms<br />Disaster Recovery<br />Site-level crisis , data and IT operations resumption<br />Backup and Restore<br />Presumes infrastructure is whole<br />97% is file/small unit related<br />High Availability<br />Presumes that the rest of the environment is active<br />Keeping the Business Running<br />
  5. 5. Business Continuity w/Virtualization<br />Business Continuity<br />Virtualization reduces BC costs and minimizes business downtime by:<br /><ul><li>increasing the availability of infrastructure
  6. 6. extending protection to more applications
  7. 7. simplifying backups, recovery and DR testing</li></ul>Primary Site<br />Secondary Site<br />High Availability<br />Disaster Recovery<br />Backup and Recovery<br />Disaster Recovery<br />Storage Array<br />Storage Array<br />VHD<br />Clustering<br />Shared Storage<br />Quick/Live Migration<br />Backup/Recovery<br />Backup/Recovery<br />Backup/Recovery<br />
  8. 8. The Architecture of Hyper-V<br />VMWorkerProcesses<br />Parent Partition<br />Child Partitions<br />Applications<br />Applications<br />Applications<br />Applications<br />User Mode<br />WMIProvider<br />VM Service<br />Windows Server 2008<br />Non-Hypervisor Aware OS<br />WindowsKernel<br />Windows Kernel<br />VSP<br />Xen-Enabled Linux Kernel<br />Windows Server 2003, 2008<br />Kernel Mode<br />IHV Drivers<br />VMBus<br />Emulation<br />Linux VSC<br />VMBus<br />VMBus<br />VSC<br />Windows Hypervisor<br />Ring -1<br />HypercallAdapter<br />“Designed for Windows” Server Hardware<br />
  9. 9. The Anatomy of a Hyper-V VM<br />.VHD – VM data<br />.AVHD – VM snapshots<br />*.BIN – Contents of VM RAM for a saved state <br />*.VSV – Saved state information (i.e., processor register data)<br />*.XML – VM configuration information in an industry-standard XML file<br />
  10. 10. The Anatomy of a Hyper-V VM<br />
  11. 11. The Anatomy of a Hyper-V VM<br />All VMs are assigned a unique GUID:<br />&lt;logical_id type=&quot;string&quot;&gt;056B19F3…FAD06C76416D&lt;/logical_id&gt; <br />All snapshots are assigned a GUID – used to identify the snapshot and construct relative paths to .AVHDs:<br />&lt;guid type=&quot;string&quot;&gt;53E0AC2C…EE46C4F495D4&lt;/guid&gt;<br />Both the virtualized NIC(s) in the VM as well as the virtual switch(es) on the host are assigned a GUID:<br />&lt;ChannelInstanceGuidtype=&quot;string&quot;&gt;{bc66…}&lt;/ChannelInstanceGuid&gt;<br />&lt;SwitchName type=&quot;string&quot;&gt;Switch-SM-847f89…&lt;/SwitchName&gt; <br />Permissions related to Hyper-VM are important to consider:<br />&lt;sid type=&quot;string&quot;&gt;S-1-5-2…&lt;/sid&gt;<br />
  12. 12. VM Backup/Recovery Challenges<br />Expense – Loading Agents in Each Guest OS<br />Protecting Virtualized Applications (Exchange, SQL, etc.)<br />VMs may Increase Backup/Restore Complexity<br />Backing up “in the guest” Versus “outside the guest” – Image or file –level recovery<br />Restoring to different hardware if necessary<br />
  13. 13. Some VM Backup Terminology<br />File-Level Backup – “In the Guest”<br />Image-Level Backup – “On the Host”<br />Application Quiescing<br />O/S Crash Consistency<br />Application Crash Consistency<br />
  14. 14. Types of VM Backups<br />Three types of Backups<br />Backing up the host system<br />May be necessary to maintain host configuration<br />But often, not completely necessary<br />The fastest fix for a broken host is often a complete rebuild<br />Backing up Virtual Disk Files<br />Fast and can be done from a single host-based backup client<br />Challenging to do file-level restore<br />Backing up VM’s from inside the VM<br />Slower and requires backup clients in every VM.<br />Resource intensive on host<br />Capable of doing file-level restores<br />
  15. 15. Challenges of Transactional DBs<br />O/S Crash Consistency is fairly easy<br />Quiesce the NTFS file system before beginning the backup<br />Application Crash Consistency is much harder<br />Tx databases like AD, Exchange and SQL don’t quiesce just because NTFS does<br />Restoration without crash consistency will lose data - DB restores into “inconsistent” state and must perform a soft recovery<br />
  16. 16. Dealing with Consistency<br />When backing up VMs, may need to consider dual approaches: file level backups and image-level backups <br />File-level = Restore Individual Files w/Tx Integrity<br />Image-level = Whole-Server Recoverability<br />Image-level backups may not provide application crash consistency!<br />MSFT and 3rd Party Solutions may integrate with VSS-aware guest OS and applications<br />Microsoft System Center Data Protection Manager<br />3rd Party Backup Solutions<br />
  17. 17. Integrating Backup w/VSS<br />VSS = Volume Shadow Copy<br />No need to power down virtual machines to do backups<br />VSS ensures a consistent state in the virtual machine<br />Must have backup integration component enabled<br />
  18. 18. Data Protection Manager 2007<br />Data Protection Manager 2007<br />Recovery Point Objective<br />15min versus RT for VSs-aware VMs<br />~1 day versus RT for non VSS-aware VMs<br />Recovery Time Objective<br />Automated Monitoring and Failover versus on-demand recovery<br />Type of Recovery Needed<br />Disaster Recovery – focus on getting back up and running with the latest copy ASAP<br />Operational Recovery & Disaster Recovery – focus on being able to recover multiple points in time<br />
  19. 19. Microsoft Data Protection Manager SP1<br /><ul><li>DPM for Hyper-V
  20. 20. Live host-level virtual machine backup In guest consistency
  21. 21. Bare metal restore
  22. 22. Rapid recovery Continuous Data Protection
  23. 23. No SAN required
  24. 24. Protects VMs without hibernation (if OS is VSS enabled)</li></ul>Secondary Site<br />Primary Site<br />Recovery<br />Up to every 15 minutes<br />WAN Connectivity<br />
  25. 25. VSS/Backup Recommendations<br />VSS in Hyper-V does not support:<br />Host-level backups of pass-through VHDs.<br />Host-level backups of iSCSI volumes in guest VMs<br />Instead, use guest-based Exchange-aware streaming backup or VSS backup <br />Data Protection Manager 2007<br />VSS in Hyper-V does support host-level backups of VHDs<br />Hardware-based VSS backups of Exchange Storage<br />Supported by the vendor, not Microsoft<br />
  26. 26. Hyper-V Backup Best Practices<br />Ensure your backup solution supports VSS<br />Support for the VSS writer in Hyper-V specifically<br />Virtual Machine Backup Best practices<br />Leverage the Hyper-V VSS writer to take online snapshots of virtual machines<br />System Center Data Protection Manager will provide Hyper-V VSS snapshots<br />Ability to quickly recover virtual machines<br />Replicate snapshots to backup location for DR<br />
  27. 27. Virtualization & High Availability<br />Traditional Non-Virtualized Environment<br /><ul><li>Downtime is bad, but affects only one workload</li></ul>Virtualized Environment<br /><ul><li>Value of the physical server goes up
  28. 28. Downtime is far worse because multiple workloads are affected</li></ul>Virtualization and High-Availability Go Hand in Hand<br />
  29. 29. Microsoft Hyper-V Quick Migration<br />Provides solutions for both planned and unplanned downtime<br />Planned downtime<br />Quickly move virtualized workloads to service underlying hardware<br />More common than unplanned<br />Unplanned downtime<br />Automatic failover to other nodes (hardware or power failure)<br />Not as common and more difficult<br />Windows Server 2008 R2 introduces Live-migration supporting movement of virtual machines between servers with no loss of service<br />
  30. 30. Quick Migration Fundamentals<br />Save state<br />Save entire virtual machine state<br />Move virtual machine<br />Move storage connectivity from origin to destination host<br />Restore state and run<br />Restore virtual machine and run<br />VHDs<br />Shared Storage<br />Network Connectivity<br />
  31. 31. Other VM Availability Scenarios<br />Guest-based VM clustering (using WSFC)<br />Cost prohibitive – requires Enterprise edition of Windows Server and shared storage<br />More complex to install/configure/manage<br />An option for cluster-aware applications<br />3rd party replication/failover solutions<br />Use software-based replication/failover to replicate VMs between Hyper-V hosts (or within VMs)<br />Double-Take for Hyper-V<br />CA XOsoft High Availability<br />SteelEyeLifeKeeper for Windows<br />
  32. 32. Virtualization Benefits<br />Downtime is Expensive<br />More Rapid Backup and Recovery<br />Quick/Live Migration/Clustering<br />Things are Complicated<br />Eliminate maintaining duplicate physical systems <br />Automate Backup, Recovery and DR processes<br />Infrastructure/People are Expensive<br />Reduce expenditure on facility and infrastructure<br />Diminish need for specialized hardware/personnel<br />
  33. 33. Some DR Terminology<br />RTO – Recovery Time Objective<br />How much data you can afford to lose…<br />RPO – Recovery Point Objective<br />How long you can afford to be down…<br />Hot site<br />Servers up and operational at remote site at all times.<br />Warm site<br />Servers pre-provisioned at remote site. Tasks to complete for failover to occur.<br />Cold site<br />Empty site and servers on retainer awaiting DR event.<br />
  34. 34. Hyper-V Recovery &quot;Value Meals&quot;<br />$$$$<br />
  35. 35. Days to Weeks Recovery<br />Use free or low-cost solutions to backup VMs at the host level (image-level backups)<br />DR site is a “cold site” with equipment available on-demand from a vendor/co-lo company<br />Store images to tape/disk and rotate off-site<br />Will need to manually restore images and fix problems ….<br />…and there will be problems!<br />
  36. 36. Hours to Days Recovery<br />Use free or low-cost solutions to backup VMs at the host level (image-level backups)<br />DR site is a “warm site” with storage available for replicated/copies VM images<br />Transfer images to off-site data storage location<br />Some tools provide off-site capabilities<br />Will need to manually restore images and fix problems ….<br />…and there will be problems!<br />
  37. 37. Minutes to Hours Recovery<br />Use replication to provide site-to site replication of VM data<br />These host-level replicated VM copies are potentially inconsistent<br />Can use SAN-based or host-based replication<br />Cost / Bandwidth trade-off<br />Less impact to WAN – changes being sent in real-time (compression/throttling)<br />Will need to attach replicated VMs to replacement equipment and fix problems<br />
  38. 38. Immediate Recovery<br />Warm or hot site is used for DR<br />Storage to storage replication installed between sites<br />3rd party replication technologies used for VM replication<br />“in the guest” for transactional integrity<br />“on the host” for all other workloads<br />Restoration is usually automated using 3rd party tools or interoperability with Windows Server Failover Clustering<br />
  39. 39. Windows Server 2008 - WSFC<br />No More Single-Subnet Limitation<br />Allows cluster nodes to communicate across network routers<br />No more having to connect nodes with VLANs!<br />Configurable Heartbeat Timeouts<br />Increase to extend geographically dispersed clusters over greater distances<br />Storage Vendor Based Solution<br />Mirrored storage between stretched locations<br />Hardware or Software based replication<br />
  40. 40. GeoCluster<br />Integrates with Microsoft Failover Clustering<br />Uses Double-Take Patented Replication<br />Extends Clusters Across Geographical Distances<br />Eliminates Single Point of Disk Failure<br />GeoCluster for Hyper-V Workloads<br />Utilizes GeoCluster technology to extend Hyper-V clustering across virtual hosts without the use of shared disk<br />Allows manual and automatic moves of cluster resources between virtual hosts<br />
  41. 41. At failover, the new active node resumes with current, replicated data<br />Only the active node accesses its disks<br />Data is replicated to all passive nodes<br />Replication<br />GeoCluster nodes use separate disks, kept synchronized by real-time replication<br />How GC Integrates w/WSFC<br />
  42. 42. question & answer<br />
  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.<br />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.<br />

×