System warning 5024 (0x000013a0).
The properties were stored but not all changes will take effect until the next time
the resource is brought online.
8. To force the changes to take effect, fail the cluster group to the passive node:
Cluster $Cluster_Name group ???Cluster Group??? /move
Moving resource group ??? Cluster Group??™...
Group Node Status
-------------------- --------------- ------
Cluster Group MB100 Online
9. Repeat this again to fail back to the original active node. Finally, check the status of the FSW
resource with the following command:
Cluster $Cluster_Name res ???Majority Node Set??? /priv
The output from the test server is:
T Resource Name Value
-- -------------------- ------------------------------ -----------------------
S Majority Node Set MNSFileShare
\\Mbfsw.exchangeexchange.
local\MNS_FSW_MBCCR
D Majority Node Set MNSFileShareCheckInterval 240 (0xf0)
D Majority Node Set MNSFileShareDelay 4 (0x4)
Chapter 12: Working with Continuous Replication
341
Configuring the Cluster Heartbeat
Four additional parameters can be changed to control failover behavior:
??‘ MNSFileShareCheckInterval
??‘ MNSFileShareDelay
??‘ HeartBeatLostInterfaceTicks
??‘ HeartBeatLostNodeTicks
The first two parameters, MNSFileShareCheckInterval and MNSFileShareDelay , control the file
share witness health checks.
Pages:
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484