Refer to above url / link. How do we tune the default Win 2008 x64 R2
Enterprise to say every 5 secs for 2-3 mins? Give steps by step &
screen shot by screen shot instructions, please.
Any caveat/shortcoming for tuning? Say the cluster will take longer
to failover in the event there's a genuine outage/crash of the active
node? How to get the best of both worlds, ie resiliency to network
slowness (during high backup traffic at night) & yet reduce the
We're running MS SQL 2008 R2 Enterprise server databases on
the pair of MSCS & ran into a few incidents of Quorum disk
(& 2 occasions of SAN disks) disappearing for several minutes.
There's also a case of duplicate IP address & we traced that it's
due to both nodes becoming active at the same time, thus the MS
SQL VIP became duplicate (owned by both nodes at the same time.
The heartbeat for the cluster nodes is set by default to send a heartbeat every second. The heartbeat configuration also by default will allow five missed heartbeats before a cluster node is deemed as unavailable. This can be configured to increase the interval and increase/decrease the threshold. This is of particular interest when using a high latency network (WAN) when implementing a geographically dispersed cluster.