June 3, 2011 at 5:00 am
All,
We have a production cluster (active/passive) where the active node had a hardware failure and was rebuilt. The cluster resources run on the second node now.
When it was rebuilt and added back to the cluster it didn't have any SQL Service packs installed on it. The previous one and current active node has SP3.
We pulled back the resources to the rebuilt node and had many problems with the applications calling it which we believe are down to SP mismatch so failed it back to the second node which is very happily running them.
We now want to install SP3 on the rebuilt node with no downtime, no removing of nodes or restarting any services/servers.
We have come across this article http://support.microsoft.com/kb/934749 which suggests you can apply updates and presumably Service packs with a /passive switch therefore not making any changes to the active node. It also suggests it will error if we tried to install SP3 on the cluster when its out of sync due to another node having a higher level of service pack.
Has anyone done this or know why we shouldn't do this during the day to get this cluster node back online and give us the comfort of having a resilient environment.
Any guidance much appreciated, never had this problem before and have no time to build a test environment to test this out.
Regards,
Steve.
June 3, 2011 at 2:53 pm
OK, for the benefit of anyone in our position in the future. The /passive successfully got our passive node up to the right SP. We suffered no downtime on our active node and are going to fail back to this newly SP'ed node on Sunday to ensure its all working. It does require a reboot of the updated node.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply