Hyper-V ile Yüksek Erişilebilirlik Senaryoları

1,336 views
1,274 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
1,336
On SlideShare
0
From Embeds
0
Number of Embeds
274
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Hyper-V ile Yüksek Erişilebilirlik Senaryoları

  1. 1. Hyper-V ile Yüksek Erişilebilirlik Senaryoları<br />Ertan GULEN<br />ertan.gulen@msn.com<br />Mshowto.org<br />
  2. 2. Failover Clustering & Hyper-V<br />Guest vs. Host Cluster<br /> Deployment & Validation<br /> Optimizing for Hyper-V<br />Datacenter Management<br />
  3. 3. Host Clustering<br />Cluster service runs inside (physical) host and manages VMs<br />VMs move between cluster nodes<br />Live Migration – No downtime<br />Quick Migration – Session state saved to disk<br />CLUSTER<br />SAN<br />
  4. 4. Why use Host Clustering?<br />Never rely on a single server for critical systems<br />“Do not put all your eggs in 1 basket”<br />Survive Host Crashes<br />VMs restarted on another node<br />Restart VM Crashes<br />VM OS restarted on same node<br />Recover VM Hangs<br />VM OS restarted on same node<br />Zero Downtime Maintenance & Patching<br />Live migrate VMs to other hosts<br />Mobility & Load Distribution<br />Live migrate VMs to different servers to load balance<br />
  5. 5. Guest Clustering<br />Cluster service runs inside a VM<br />Apps and services inside the VM are managed by the cluster<br />Apps move between clustered VMs<br />CLUSTER<br />iSCSI<br />
  6. 6. Why use Guest Clustering?<br />Application Health Monitoring<br />App or service within VM crashes or hangs and moves to another VM<br />Application Mobility<br />Apps or services moves to another VM for maintenance or patching of guest OS<br />CLUSTERc<br />iSCSI<br />
  7. 7. Guest vs. Host: Health Detection<br />
  8. 8. Guest vs. Host: Storage Options<br />
  9. 9. Failover Clustering & Hyper-V<br />Guest vs. Host Cluster<br /> Deployment & Validation<br /> Optimizing for Hyper-V<br />Datacenter Management<br />
  10. 10. SKUs & Hyper-V Server<br />Microsoft Hyper-V Server 2008 R2<br />FREEHost OS – Download it today!<br />Built on Server Core for even higher availability<br />Failover Clustering, Hyper-V, CSV, Live Migration<br />16-node Support<br />More information: http://www.microsoft.com/hyper-v-server/en/us/default.aspx<br />All solutions still have 2 requirements for support:<br />Every component must be logoed <br />The entire solution must pass “Validate”<br />
  11. 11. Validating a Cluster<br /><ul><li>For Microsoft support, cluster must pass the built-in Validate a Cluster Configuration (“Validate”) test
  12. 12. Run during configuration or after deployment
  13. 13. Best practices analyzed if run on configured cluster
  14. 14. Series of end-to-end tests on all cluster components
  15. 15. Configuration info for support and documentation
  16. 16. Networking issues
  17. 17. Troubleshoot in-production clusters
  18. 18. More information http://go.microsoft.com/fwlink/?LinkID=119949</li></li></ul><li>PowerShell Support<br />Improved Manageability<br />Run Validate<br />Easily Create Clusters & HA Roles<br />Generate Dependency Reports<br />Built-in Help (Get-Help Cluster)<br />Hyper-V Integration<br />Create VMs: Add-ClusterVirtualMachineRole<br />Quick migration: Move-ClusterGroup<br />Live migration: Move-ClusterVirtualMachineRole<br />Add a disk to CSV: Add-ClusterSharedVolume<br />Move CSV disk: Move-ClusterSharedVolume<br />Update VM Configuration: Update-ClusterVirtualMachineConfiguration<br />Server Core, Hyper-V Server 2008 R2& RSAT Client<br />Replaces cluster.exe as the CLI tool<br />
  19. 19. Failover Clustering & Hyper-V<br />Guest vs. Host Cluster<br /> Deployment & Validation<br /> Optimizing for Hyper-V<br />Datacenter Management<br />
  20. 20. Hyper-V<br />Only<br />Cluster Shared Volumes<br />Data over any network <br />Coordinator Node<br />Every node can access storage<br />SAN<br />1 LUN : Many VMs<br />VHD<br />VHD<br />VHD<br />
  21. 21. Live Migration<br />Memory content is copied to new server<br />Live Migrate<br />SAN<br />May be additional incremental data copies until data on both nodes is essentially identical<br />Entire VM memory copied<br />VHD<br />
  22. 22. Live Migration<br />Client directed to new host<br />SAN<br />Session state is maintained<br />No reconnections necessary<br />Clients stay connected to a “live” VM<br />ARP redirects clients to new node<br />Old VM deleted after success<br />VHD<br />
  23. 23. Configuring VM Health Monitoring<br />Enable VM heartbeat setting<br />Requires Integration Components (ICs) installed<br />Health check for VM OS from host<br />User-Mode Hangs<br />System Crashes<br />CLUSTER<br />SAN<br />
  24. 24. NICs & Networks in a Cluster<br />Best Solution<br />Internal / Cluster / CSV / ‘Heartbeat’<br />Public network for clustered Apps, Services & VMs<br />Storage: iSCSI<br />Hyper-V: VM Guest Management<br />Hyper-V: Live Migration<br />Minimum is 2 networks:<br />Internal & Live Migration<br />Public & VM Guest Management<br />Use ‘Network Prioritization’ to configure your networks<br />
  25. 25. Settings: Dynamic Memory<br />WS2008 R2 SP1 & Hyper-V Server 2008 R2SP1<br />Upgrade the Guest Integration Components <br />Higher VM density across all nodes<br />Memory allocated to VMs is dynamically adjusted in real time<br />“Ballooning” makes memory pages non-accessible to the VM, until they are needed<br />Does not impact Task Scheduler or other memory-monitoring utilities<br />Memory Priority Value is configurable per VM<br />Higher priority for those with higher performance requirements<br />Ensure you have enough free memory on other nodes for failure recovery<br />
  26. 26. Refreshing the VM Configuration<br />Make configuration changes through Failover Cluster Manager or SCVMM<br />Hyper-V Manager is not cluster aware, changes will be lost<br />“Refresh virtual machine configuration”<br />Looks for any changes to VM or Cluster configuration<br />PS > Update-ClusterVirtualMachineConfiguration<br />Storage<br />Moves disks into correct group with new VMs<br />Ensures VM on correct CSV disk with updated paths<br />Network<br />Applies changes to cluster network properties<br />Checks live migration compatibility<br />Several other checks performed<br />
  27. 27. Failover Clustering & Hyper-V<br />Guest vs. Host Cluster<br /> Deployment & Validation<br /> Optimizing for Hyper-V<br />Datacenter Management<br />
  28. 28. Virtual Machine Density<br />1000 VMs per Cluster<br />Deploy them all across any number of nodes<br />384 VM/node limit<br />Planning Considerations:<br />Hardware Limits<br />Hyper-V Limits<br />Reserve Capacity<br />Storage I/O & Latency<br />
  29. 29. SCVMM: Live Migration<br />Detects if Live migration can be done<br />Node placed into ‘Maintenance Mode’<br />Live-migrate (default) all running HA VMs Serialized multiple live migrations<br />Save-State (optional)<br />Ideal for host maintenance and patching<br />Automatically retries live migrations if a node is busy<br />
  30. 30. SCVMM: Quick Storage Migration<br />Ability to migrate VM storage to new location<br />Minimizes downtime during transfer<br />Handled in a single seamless action<br />
  31. 31. SCOM: Performance & Resource Optimization (PRO)<br />Alleviate the effects of host-level failure<br />Ensure efficient use of resources in the virtualized environment<br />Allow VMM Admins to react and manage resources independently<br />Integrated with SCVMM<br />SCOM sends alters to SCVMM to trigger live migration of VMs<br />
  32. 32. Putting it Together<br />
  33. 33. Teşekkürler..<br />Ertan GULEN<br />ertan.gulen@msn.com<br />www.mshowto.org<br />www.tribula.com<br />

×