Slide 1

Slide 2

Slide 3

Slide 4

Slide 5

But what if there is a catastrophic event? Fire, flood, earthquake

Slide 6

apps fail over to a separate physical location Servers in separate locations in the same cluster

Slide 7

Recovery Time Objective (RTO)Recovery Point Objective (RPO)

Slide 8

Slide 9

Slide 10

Slide 11

WAN Different datacenters (usually) equates to different subnets Longer distance means greater network latency

Slide 12

PropertyDefaultRecommendedDescription SameSubnetDelay 11Frequency heartbeats (HB) sent SameSubnetThreshold 510Missed HB before interface considered down CrossSubnetDelay 11Frequency HB sent to nodes on dissimilar subnets CrossSubnetThreshold 520 Missed HB before interface considered down to nodes on dissimilar subnets PowerShell: (Get-Cluster).SameSubnetThreshold = 10 (Get-Cluster).CrossSubnetThreshold = 20

Slide 13

Dependencies in Cluster Validation Report Network Name Resource IP Address Resource A IP Address Resource B OR

Slide 14

10.10.10.10 DNS Replication Record Created Record Updated Record Obtained 20.20.20.20 DNS Client access point fails across subnets Client needs new address Nodes in dissimilar subnets

Slide 15

20.20.20.20 10.10.10.10 Network Virtualization 30.30.30.30

Slide 16

PowerShell syntax: Get-ClusterResource ClusNN | Set-ClusterParameter RegisterAllProvidersIP 1 Get-ClusterResource ClusNN | Set-ClusterParameter HostRecordTTL 300

Slide 17

10.10.10.10 VM = 10.10.10.111 20.20.20.20 DNS

Slide 18

DNS Server 1 DNS Server 2 FS = 10.10.10.111 10.10.10.10 VLAN DNS

Slide 19

10.10.10.10 20.20.20.20 DNS Server 1 DNS Server 2 VM = 30.30.30.30 30.30.30.30 DNS

Slide 20

ValueDescription 0Clear Text 1Signed (default) 2Encrypted PowerShell syntax: (Get-Cluster). SecurityLevel = 2

Slide 21

Adjust intra-node heartbeat thresholds Understand NetName Resource Configuration Optimize Client Reconnection on CAP Failover Encrypt intra-node communication over unsecure WANs

Slide 22

Slide 23

Each node can have 1 vote Witness can only have 1 vote

Slide 24

Vote 5 1 2 3 4 Site 2 Down!!! Site 1 can reach Cloud Witness! Cluster Survives!

Slide 25

Azure Witness

Slide 26

Slide 27

Cloud WitnessFile Share Witness Share the same arbitration logic Do not keep copy of cluster database

Slide 28

Cluster Site 1 Site 2

Slide 29

1 2 3 4 Vote Loss of Primary Site: Start-ClusterNode -ForceQuorum Recovery of Primary Site: Start-ClusterNode -PreventQuorum

Slide 30

PowerShell syntax: Get-ClusterGroup MyVM | Set-ClusterOwnerNode Node1, Node2

Slide 31

Recommended to use Cloud Witness When no access to Azure use File Share Witness in a 3 rd site Automatic failover Keep number of nodes on primary and secondary sites equal Manual failover Remove votes of nodes on secondary site

Slide 32

Slide 33

Slide 34

Chicago (you are here) NYC Can you hear me now?

Slide 35

Replication Block-level, volume-based Synchronous & asynchronous SMB 3.1.1 transport Flexibility Any Windows volume Any fixed disk storage Any storage fabric Managemen t Failover Cluster Manager Windows PowerShell WMI End to end MS Storage Stack

Slide 36

Slide 37

Cluster Site1 Site2

Slide 38

Applications (local or remote) Source Server Node (SR) Data Log 1 t 2 Destination Server Node (SR) Data Log t1t1 3 2 5 4

Slide 39

Slide 40

Slide 41

Slide 42

Slide 43

Slide 44

Slide 45

Slide 46

Slide 47

Slide 48