Service not starting automatically in another node
i have created 1 2-node sql cluster. there total 3 vms (in hyper-v).
1. node1: current owner of sqlserver , msdtc services.
2. node2
3. node3: starwind iscsi installed.
if turn off/save node1 (which hyper-v vm), sqlserver or msdtc service not moving node2 automatically , cluster down.
my question is:
a) intended behaviour this? if not, how should make working. how move service node automatically ?
which quorum model using , quorum (disk or file share witness)? seems using node majority , when node goes down cluster loses majority votes , cluster automatically shuts down (on second node).
to correct problem use a node , file share witness or node , disk witness quorum model.
Windows Server > High Availability (Clustering)
Comments
Post a Comment