Windows fail-over clustering is very useful for servers fail over, when configuring this function some common issues we might encounter, I shared the solutions as follows:
1) Cluster quorum setting cannot be successful.
Most likely, it is due to access permission of the 3th share folders. We need to check whether the target folder permission includes all the related machine name(especially the fail over cluster name) .As the sample below, configure all the related nodes
have full control authority.
2) Cannot remove old fail over cluster due to core resource cannot be deleted
If cannot delete the core resource, delete 2 registry as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusSvc
Then remove the fail over cluster roles, and also remove the related fail over cluster virtual name in the AD machine list.
3)When Setting service access point, cannot use same IP as failover cluster access point IP
It is very ridiculous, use 2 ip to fulfill one clustering function. So solution is after setup fail over cluster, remove IP under server name.
Then add service roles, configure the IP under service role node.
