27
Hyper-V ile Yüksek Erişilebilirlik Senaryoları Ertan GULEN e [email protected] Mshowto.org

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

Embed Size (px)

DESCRIPTION

 

Citation preview

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

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

Ertan [email protected]

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

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

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

CLUSTER

Host Clustering

Cluster service runs inside (physical) host and manages VMsVMs move between cluster nodes

Live Migration – No downtimeQuick Migration – Session state saved to disk

SAN

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

Why use Host Clustering?

Never rely on a single server for critical systems“Do not put all your eggs in 1 basket”

Survive Host CrashesVMs restarted on another node

Restart VM CrashesVM OS restarted on same node

Recover VM HangsVM OS restarted on same node

Zero Downtime Maintenance & PatchingLive migrate VMs to other hosts

Mobility & Load DistributionLive migrate VMs to different servers to load balance

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

CLUSTER

Guest Clustering

Cluster service runs inside a VMApps and services inside the VM are managed by the clusterApps move between clustered VMs

iSCSI

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

CLUSTERc

Why use Guest Clustering?

Application Health MonitoringApp or service within VM crashes or hangs and moves to another VM

Application MobilityApps or services moves to another VM for maintenance or patching of guest OS

iSCSI

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

Guest vs. Host: Health Detection

Fault Host Cluster Guest Cluster

Host Hardware Failure

Parent Partition Failure

VM Failure

Guest OS Failure

Application Failure

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

Guest vs. Host: Storage Options

Storage Host Cluster Guest Cluster

Fibre Chanel (FC)

Serial Attached SCSI (SAS)

iSCSI

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

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

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

SKUs & Hyper-V Server

Microsoft Hyper-V Server 2008 R2FREE Host OS – Download it today!Built on Server Core for even higher availabilityFailover Clustering, Hyper-V, CSV, Live Migration16-node SupportMore 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”

Specification Hyper-V Server Enterprise Datacenter

Failover Cluster Nodes 16 16 16

VM Guest Licenses 0 4 Unlimited

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

Validating a Cluster

• For Microsoft support, cluster must pass the built-in Validate a Cluster Configuration (“Validate”) test

• Run during configuration or after deployment• Best practices analyzed if run on configured cluster

• Series of end-to-end tests on all cluster components• Configuration info for support and documentation• Networking issues• Troubleshoot in-production clusters

• More information http://go.microsoft.com/fwlink/?LinkID=119949

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

PowerShell Support

Improved ManageabilityRun ValidateEasily Create Clusters & HA RolesGenerate Dependency ReportsBuilt-in Help (Get-Help Cluster)

Hyper-V IntegrationCreate VMs: Add-ClusterVirtualMachineRoleQuick migration: Move-ClusterGroupLive migration: Move-ClusterVirtualMachineRoleAdd a disk to CSV: Add-ClusterSharedVolumeMove CSV disk: Move-ClusterSharedVolumeUpdate VM Configuration: Update-ClusterVirtualMachineConfiguration

Server Core, Hyper-V Server 2008 R2 & RSAT Client

Replaces cluster.exe as the CLI tool

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

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

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

Cluster Shared VolumesData over any network

VHD VHD VHD

Coordinator Node

1 LUN : Many VMs

Hyper-V

Only

Every node can access storage

SAN

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

Live Migration

Memory content is copied to new server

Entire VM memory copied

Live Migrate

May be additional incremental data copies until data on both nodes is essentially identical

VHD

SAN

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

Live Migration

Session state is maintainedNo reconnections necessaryClients stay connected to a “live” VM

VHD

SANARP redirects clients to new nodeOld VM deleted after success

Client directed to new host

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

CLUSTER

Configuring VM Health Monitoring

Enable VM heartbeat settingRequires Integration Components (ICs) installed

Health check for VM OS from hostUser-Mode HangsSystem Crashes

SAN

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

NICs & Networks in a Cluster

Best SolutionInternal / Cluster / CSV / ‘Heartbeat’Public network for clustered Apps, Services & VMsStorage: iSCSIHyper-V: VM Guest ManagementHyper-V: Live Migration

Minimum is 2 networks:Internal & Live MigrationPublic & VM Guest Management

Use ‘Network Prioritization’ to configure your networks

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

Settings: Dynamic MemoryWS2008 R2 SP1 & Hyper-V Server 2008 R2 SP1

Upgrade the Guest Integration Components

Higher VM density across all nodesMemory allocated to VMs is dynamically adjusted in real time

“Ballooning” makes memory pages non-accessible to the VM, until they are neededDoes not impact Task Scheduler or other memory-monitoring utilities

Memory Priority Value is configurable per VMHigher priority for those with higher performance requirements

Ensure you have enough free memory on other nodes for failure recovery

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

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 configurationPS > Update- ClusterVirtualMachineConfiguration

StorageMoves disks into correct group with new VMsEnsures VM on correct CSV disk with updated paths

NetworkApplies changes to cluster network propertiesChecks live migration compatibility

Several other checks performed

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

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

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

Virtual Machine Density1000 VMs per ClusterDeploy them all across any number of nodes384 VM/node limitPlanning Considerations:

Hardware LimitsHyper-V LimitsReserve CapacityStorage I/O & Latency

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

SCVMM: Live MigrationDetects if Live migration can be doneNode placed into ‘Maintenance Mode’

Live-migrate (default) all running HA VMs Serialized multiple live migrationsSave-State (optional)Ideal for host maintenance and patching

Automatically retries live migrations if a node is busy

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

SCVMM: Quick Storage Migration

Ability to migrate VM storage to new locationMinimizes downtime during transferHandled in a single seamless action

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

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

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

Putting it Together