SQL Server does not failback to the primary node We are running SQL Server 2008 R2 on a Windows Server 2008 R2 two-node cluster.  

My choice of machine is primary, and the secondary is just a low-end machine for contingency planing.  

We had a failover the last day during night time and when I came to the office the next morning, I noticed that SQL Server service did not failback to the primary machine although it came back online.  

All settings seems to be in place:  


Attachment 1 shows the general tab of SQL Server service properties dialog box from Server Manager - > Failover Cluster Manager. Both machines are checked, primary being at the top. 

   
Attachment 2 shows failover tab of the same dialog box. Immediate failback is activated.  

  


How can I modify these settings so that whenever the primary comes back, system will failback onto it.
I set up a virtual lab environment simulating a clustered network where I unticked one of the nodes as the preferred owner. I can confirm that whenever the ticked node goes offline, the unticked one comes into play and the system failbacks onto the ticked node once it comes online again.