Hi all,
I used to be quite proficient in Windows 2000/2003 clustering. I wanted to update my skill set so
I have setup a 2008 R2 cluster at my home. Please note that this is in my home and is not exactly an ideal production environment. I like to setup services at home for practice. (I will REALLY miss Technet)
For my shared storage I am using a Windows 2012 server with iscsi target. (HP DL360G5) On all servers I have iscsi going over the same teamed nics as the network traffic. I know that this is not recommend/supported but it "seems" to be working ok for me.
Both nodes are domain controllers. Both are also DFS servers and they run DFS replication. They are both also DNS servers. None of these services are clustered. (The servers are an ML330G6 and DL385G5)
On node A I am also running Exchange 2010 (not clustered)
I have both nodes connected via iscsi to the virtual drives of the storage server.
The iscsi target has 3 shared drives for my clustered services.
DHCP and Print. (I also created a quorum disk to play with disk only Quorum)
After many trials and tribulations I am almost steady. I can failover back and forth between the nodes all day from the cluster administrator tool successfully. I have also tested failing over to node B and then booting node B. The resources successfully
transfer over to node A. My issue is when I have node A as the owner of the resources and then I boot node A. The resources don't failover to node B. The cluster admin tool (running on node B) eventually hangs. Node B is able to finally grab the resources
when node A comes back online. (By itself. I don't force any failing over when this happens)
I have tried changing the Quorum mode. I tried Node and Disk Majority (using one of the shared storage disks as a witness). I tried Node and File Share majority (using the netlogon share on the storage server as the witness) and I also tried Disk Only. (created
a third quorum shared disk)
Any clues?
Thanks.