I have a lab environment with the following setup:
Host: WS 2016 with hyper V installed.
2 VM's (WS2016) clustered running Fileshare with no witness (It is a lab environment just for testing purposes).
ISCSI disk has been created on a third VM which is being used as Fileshare.
CASE:1
Cluster running with both the nodes up. Current owner of the Role: say SERVER1.
I shutdown the server and the new owner of the role is SERVER2. CLUSTER IS STILL UP AND RUNNING.
CASE:2
With the current role owner being SERVER2 and SERVER1 being currently shut down. If I shutdown SERVER2 now, the cluster is going to stop (very obvious).
Upon starting SERVER1 again, the cluster is not up. SERVER1 shows the ISCSI disk to be offline. Tried manually starting the cluster but still it does not start (I could not check the votes as I could not access the cluster node option in Failover cluster manager, as the cluster is Stopped). Cluster events does not show any data.
CASE:3
Upon starting SERVER2, the cluster starts automatically and the Owner Node is SERVER2.
Questions:
1) Why the cluster does not start in case:2 ? Is it because of the voting ? How do I troubleshoot ?
2) Is this a normal behaviour ? How do I override it ?
3) What are your advise for the best practices when working with WSFC ?