1. Hyper-V ile Yüksek Erişilebilirlik Senaryoları Ertan GULEN ertan.gulen@msn.com Mshowto.org

2. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

3. Host Clustering Cluster service runs inside (physical) host and manages VMs VMs move between cluster nodes Live Migration – No downtime Quick Migration – Session state saved to disk CLUSTER SAN

4. Why use Host Clustering? Never rely on a single server for critical systems “Do not put all your eggs in 1 basket” Survive Host Crashes VMs restarted on another node Restart VM Crashes VM OS restarted on same node Recover VM Hangs VM OS restarted on same node Zero Downtime Maintenance & Patching Live migrate VMs to other hosts Mobility & Load Distribution Live migrate VMs to different servers to load balance

5. Guest Clustering Cluster service runs inside a VM Apps and services inside the VM are managed by the cluster Apps move between clustered VMs CLUSTER iSCSI

6. Why use Guest Clustering? Application Health Monitoring App or service within VM crashes or hangs and moves to another VM Application Mobility Apps or services moves to another VM for maintenance or patching of guest OS CLUSTERc iSCSI

7. Guest vs. Host: Health Detection

8. Guest vs. Host: Storage Options

9. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

10. SKUs & Hyper-V Server Microsoft Hyper-V Server 2008 R2 FREEHost OS – Download it today! Built on Server Core for even higher availability Failover Clustering, Hyper-V, CSV, Live Migration 16-node Support More information: http://www.microsoft.com/hyper-v-server/en/us/default.aspx All solutions still have 2 requirements for support: Every component must be logoed The entire solution must pass “Validate”

12. Run during configuration or after deployment

13. Best practices analyzed if run on configured cluster

14. Series of end-to-end tests on all cluster components

15. Configuration info for support and documentation

16. Networking issues

17. Troubleshoot in-production clusters

19. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

20. Hyper-V Only Cluster Shared Volumes Data over any network Coordinator Node Every node can access storage SAN 1 LUN : Many VMs VHD VHD VHD

21. Live Migration Memory content is copied to new server Live Migrate SAN May be additional incremental data copies until data on both nodes is essentially identical Entire VM memory copied VHD

22. Live Migration Client directed to new host SAN Session state is maintained No reconnections necessary Clients stay connected to a “live” VM ARP redirects clients to new node Old VM deleted after success VHD

23. Configuring VM Health Monitoring Enable VM heartbeat setting Requires Integration Components (ICs) installed Health check for VM OS from host User-Mode Hangs System Crashes CLUSTER SAN

24. NICs & Networks in a Cluster Best Solution Internal / Cluster / CSV / ‘Heartbeat’ Public network for clustered Apps, Services & VMs Storage: iSCSI Hyper-V: VM Guest Management Hyper-V: Live Migration Minimum is 2 networks: Internal & Live Migration Public & VM Guest Management Use ‘Network Prioritization’ to configure your networks

25. Settings: Dynamic Memory WS2008 R2 SP1 & Hyper-V Server 2008 R2SP1 Upgrade the Guest Integration Components Higher VM density across all nodes Memory allocated to VMs is dynamically adjusted in real time “Ballooning” makes memory pages non-accessible to the VM, until they are needed Does not impact Task Scheduler or other memory-monitoring utilities Memory Priority Value is configurable per VM Higher priority for those with higher performance requirements Ensure you have enough free memory on other nodes for failure recovery

26. Refreshing the VM Configuration Make configuration changes through Failover Cluster Manager or SCVMM Hyper-V Manager is not cluster aware, changes will be lost “Refresh virtual machine configuration” Looks for any changes to VM or Cluster configuration PS > Update-ClusterVirtualMachineConfiguration Storage Moves disks into correct group with new VMs Ensures VM on correct CSV disk with updated paths Network Applies changes to cluster network properties Checks live migration compatibility Several other checks performed

27. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

28. Virtual Machine Density 1000 VMs per Cluster Deploy them all across any number of nodes 384 VM/node limit Planning Considerations: Hardware Limits Hyper-V Limits Reserve Capacity Storage I/O & Latency

29. SCVMM: Live Migration Detects if Live migration can be done Node placed into ‘Maintenance Mode’ Live-migrate (default) all running HA VMs Serialized multiple live migrations Save-State (optional) Ideal for host maintenance and patching Automatically retries live migrations if a node is busy

30. SCVMM: Quick Storage Migration Ability to migrate VM storage to new location Minimizes downtime during transfer Handled in a single seamless action

31. SCOM: Performance & Resource Optimization (PRO) Alleviate the effects of host-level failure Ensure efficient use of resources in the virtualized environment Allow VMM Admins to react and manage resources independently Integrated with SCVMM SCOM sends alters to SCVMM to trigger live migration of VMs

32. Putting it Together

33. Teşekkürler.. Ertan GULEN ertan.gulen@msn.com www.mshowto.org www.tribula.com