August 5, 2013 at 8:24 am
Good morning,
W have a SQL 2008 R2 cluster set up as an active/active. We had the default instance running on the A side and three other instances running on the B. Before I got here, they needed to patch to SP2 CU5 to fix an issue with one of the applications using the server. The A side was successfully patched, but there was a problem on the B side.The admin had to restore the operating system from backup. This caused some of the original installation files to disappear. Consequently the update could not find necessary files and failed. The two sides are now at different version levels. The cluster was switched to an active/passive with the B side being the passive.
I am not sure how to fix this issue. I am thinking we may need to do a complete reinstall of SQL on B, but that is convoluted with 4 different instances and analysis services and reporting services all installed.
I have not worked with a sql cluster since 2007. (SQL2005).
Any ideas?
Thanks
Mike
“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey
___________________________________________________________________
August 6, 2013 at 8:22 am
I personally would remove the passive node from the cluster and reinstall. Remember when adding a node to the cluster all setup options are taken from the active node so it should be a case of Next Next Next on the install wizard.
Once reinstalled, patch the passive node to the correct level then perfom a failover enusing all comes back online.
SSRS is not cluster aware so you should not really have any problems there, if the servers only host the SSRS databases and not the front end aspect then you should have no issues. But if you are using both as SSRS Web servers in a scaleout deployment you will need to recreate all the settings on your current passive node.
MCITP SQL 2005, MCSA SQL 2012
August 6, 2013 at 11:00 am
That is what we are currently planning on doing.
Thanks.
Mike
“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey
___________________________________________________________________
August 6, 2013 at 10:32 pm
I actually had a similar issue once where the first node had an error during cluster setup but the added node didn't so to install service packs i had to fail everything over to the second node then opted for a complete rebuild of the first node and rejoined it to the cluster.
August 19, 2013 at 8:33 am
This was exactly what we had to do. We evicted the node from the cluster,
completely rebuilt the server, joined it to the cluster, then reinstalled sql and patched to correct level.
Everything is now at the same level and failover works correctly.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply