Clustering - 1 - Planning

7/28/2019 Clustering - 1 - Planning

1/17

Clustering

Planning

Microsoft IT Camps - Virtualization


2/17

Hyper-V High Availability Load Balancing

Windows Server Network Load Balancing (NLB) Simple L2 software-based load-balancer

Load-balance within a host and across hosts (assuming switches support

Hardware Load Balancer Full-featured, but often expensive

Replication

Copy VMs to another host Backup / Restore

Save running VM

Restore if it crashes on the same host or in a different datacenter

Hyper-V Primarily uses Failover Clustering


3/17

Failover Clustering & Hyper VM High-Availability

Automatic failover & recovery

Hardware health detection

Host OS health detection

VM health detection

Application/service health detection

VM Mobility Live migration

Quick migration Failover

Deployment Flexibility VM not bound to a single host


4/17

Failover Clustering SKUs Windows Server 2008 R2

Enterprise Datacenter

Itanium

Microsoft Hyper-V Server 2008 R2

FREE Host OS Download it today!

Built on Server Core for even higher availability from fewer Failover Clustering, Hyper-V, CSV, Live Migration

More information: http://www.microsoft.com/hvs

SKU Differences Enterprise Datacenter Itanium Hyper-V Server

Failover Cluster Nodes 16 16 8 16

VM Guest Licenses 4 Unlimited Unlimited* 0
http://www.microsoft.com/hvshttp://www.microsoft.com/hvs


5/17

Failover Clustering Basics1. Deploy redundant hardware everywhere

2. Shared storage accessible by all nodes3. Clustered application writes data to shared storage so all nodes can assess it

4. A registry hive containing current cluster configuration information is replicated t

5. Nodes monitor the health of other nodes

6. If a node fails, the health check will fail, and a failover will happen

7. Another node knows what the failed node was hosting through the registry and sapplication

8. The application reads its saved data from the shared storage

9. Client connects to app on new node

10. Clients may experience a slight interruption in service during failover but none dumigration (of a VM)


6/17

VMs &

Workloads

Simulated Failover

Public

Shared

Storage


7/17

Cluster Storage

Requires a Storage Area Network (SAN)

SCSI-3 Commands

Basic GPT and MBR disks supported

Multipath IO (MPIO) recommended

Persistent Reservations (PRs) required

Fibre Channel

(FC)

Fibre Channel

over Ethernet

(FCoE)

Serial-Attached

SCSI (SAS)


8/17

Cluster Networking Integrated with Windows Server TCP/IP Stack

Multiple networks for added redundancy Separate networks by function

Public Network

Internal Cluster Network (health checks, cluster communic

Hyper-V Live Migration & Management

Storage (iSCSI, FCoE) Backup

IPv4, IPv6 & IPv6 Tunneling

DHCP or Static IP Addresses


9/17

Quorum Overview

Node Majority

Node and Disk Majority

Node and File Share Majority

Disk Only (not recommended)

Vote Vote

Cluster membership model to avoid partitions and split-brain

Majority is greaterthan 50%

Always have an odd number of votes and at least 3 voters

Possible voters: Nodes (1 each) + 1 Witness (Disk or File Share)

4 Quorum Types

Cluster Disk

Disk Witness

Rem

File

VoteVote

Vote


10/17

Supported Roles and Featu Common

Hyper-V SQL

Exchange

File Server

Also Ship In Box

DFS-Namespace

DFS-Replication

DHCP

DTC

iSNS

MSMQ

NFS

Print

Remote Desktop Connection Broker

WINS

Custom Scripts

Active Directory CS Active Directory RMS

HPC

IIS WWW & FTP

iSCSI Target

Generic Containers

Generic Application

Generic Script

Generic Service

Other Server

3rd Party

Custom LOB Applications

Etc


11/17

Cluster Groups VMs

Virtual Machine

Virtual Machine Configuration File Information about the VMs features

Cluster Shared Volumes Cluster disk visible by all nodes

Other Workloads (File Server, DHCP, etc.) Network Name (NetName)

Easy name for clients to connect

IP Address

IP address associated with NetName Uses DHCP if enabled in environment

Service / Application Highly-available service or app

Physical Disk Resource Shared storage so all

nodes can access data


12/17

Host vs. Guest Clustering

Cluster service runs inside (physical)host and manages VMs

VMs move between cluster nodes

Cluster service runs insid

Apps and services insidemanaged by the cluster

Apps move between clu

Guest ClusterinHost Clustering

SAN

Cluster

iSCSI

Cluster


13/17

What Host Clustering Delive Avoids a single point of failure when consolidating

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


14/17

What Guest Clustering Deliv Application Health Monitoring

App or service within VM crashes or hangs and moves to a Application Mobility

Apps or services moves to another VM for maintenance orguest OS

iSCSI

Cluster


15/17

Combining Host & Guest Clust Best of both worlds for flexibility and protection

VM high-availability & mobility between physical nodes Application & service high-availability & mobility between VMs

Increases complexity

CLUSTER CLUSTERiSCSI

Guest Cluster

SAN SAN


16/17

Mixing Physical and Virtua Mixing physical & virtual nodes is supported

Must still pass Validate

Requires iSCSI storage

Scenarios Spare node is a VM in a Private Cloud

Shared host running multiple spare nodes as VMs

Test environment with limited hardware

iSCSI


17/17

Takeaways

Failover Clustering is the primary high-availability technology for Hyper-V

Clustering has extra considerations aro

shared storage and networking

Almost any datacenter workload can ru

Failover Cluster

Clustering - 1 - Planning

Documents

Transcript of Clustering - 1 - Planning