We have a 4 note active cluster for our SQL server production environment.
A few weeks ago we had a maintenance window for windows updates, so i updated SQL4 first, then i movewd all our instances to that host, and updated SQL3 - reboot - SQL2 - reboot - SQL 1 - reboot and then redistributed all the instances again.
now it seems that 1 of our instances no longer want to start on node 4, it will infact only run on node 1...
that is not even close to high availability, so it must be corrected, but how?
all the disks go online, the networkname too, aswell as the cluster share service, but the SQL server just says "Failed"