How would you connect to manage clustered SQL resources if the virtual IP and virtual name resources are down for MSCS and the SQL Cluster group?


I remember the client telling me they apparently spent 2 days trying to figure it out but wasn't able to. I thought about it for a few seconds, opened up an RDP session to both of the nodes, figured out which one was active and owned the quorum, opened up cluster administrator, then typed: localhost in the connect to.
The client was amazed. The interviewee was stumped but managed to answer it after a few minutes. :)
2 comments:
probably would have been more impressed if you'd just typed a period in cluster admin to get the cluster service up...
Thanks for these instructions ! I really appreciated the read and shall be dropping by from time to time now.
Post a Comment