Professional Documents
Culture Documents
8 Failover Clusters Using Windows Server 2016 m8 Slides
8 Failover Clusters Using Windows Server 2016 m8 Slides
8 Failover Clusters Using Windows Server 2016 m8 Slides
Bruce Mackenzie-Low
MASTER TECHNOLOGIST
Bruce.Mackenzie@q.com
Module
Overview Cloud Witness
Storage Replica
Site-aware Clusters
Implementing Sites
Preferred Sites
Cloud Witness
Storage-agnostic
Block-level replication
Synchronous or asynchronous
Works with site-aware failover clusters
Storage Replica Details
Windows Feature installed via Server Manager or PowerShell
Supported in Stretch Clusters, Cluster to Cluster, or Server to Server
Source volume (data and log) are replicated to destination volumes
Destination volumes are dismounted during replication (i.e. no access)
Offline
Data Data Data Data
Replicates
Failover Affinity:
• Roles failover to a node within the same site before
failing over to a different site
Storage Affinity:
Virtual Machines will follow their CSV storage by being
placed in the same site with their storage
VMs will live migrate to the same site as their storage
after 1 minute of the storage being moved
Quorum Behavior
Split Brain (even split between sites with no witness) favors the
Preferred Site
Nodes in the DR site drop out of cluster membership
Allows the cluster to survive a simultaneous 50% loss of votes
LowerQuorumPriorityNodeID property is deprecated in Windows
Server 2016
Cross-site Heartbeat Thresholds
PowerShell cmdlets:
New-ClusterFaultDomain
Get-ClusterFaultDomain
Set-ClusterFaultDomain
Remove-ClusterFaultDomain
Creating Cluster Fault Domains
Two step process
1. Create the cluster fault domain
2. Assign fault domain membership
Key fields:
Name – name of the fault domain (e.g. Primary, Secondary)
Note:
You must remove all fault domain members before removing the site
Do not remove the “Node” fault domain type
Demo
Demonstrate implementing sites
(Cluster Fault Domains)
Establishing Cluster Preferred Site
For example:
(Get-Cluster).PreferredSite = Primary
Establishing Cluster Group Preferred Site
For example:
(Get-ClusterGroup –Name VM1).PreferredSite = Primary
(Get-ClusterGroup –Name VM2).PreferredSite = Secondary
Placement Priority
Groups in a cluster are placed based on the following priority:
1. Traditional “Preferred Owners” takes precedence
2. Storage affinity site (group/role follows storage)
3. Group preferred site (prefer group sites over cluster site)
4. Cluster preferred site
Note:
Microsoft does not recommend using both Preferred Owners and Preferred Sites
(use one or the other)