March 23, 2009 at 2:56 pm
Hello,
We have a Veritas active/passive failover cluster set up. We have run into issues were hotfixes could not finish successfully because it was installed on the inactive node.
Is there a way to determine if the hotfix requires the active node?
Also, I am wondering how others handle this. The standard here is to apply to the passive node, wait a day to make sure it doesn't crash, failover, and then apply the passive node again the next day. When it requires an active node - what procedure do you recommend?
Windows 2003 R2 (64-bit) with Sql Server 2005 SP2 (64-bit)
Thanks in advance!
March 23, 2009 at 10:37 pm
When applying hot fix to active node SQL Server automatically applies to passive node (node defined as passive node for the instance you are patching) Only time you have to run the hot fix on the passive node is when there are desktop tools and such involved as they do not get patched over network.
Thanks.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 24, 2009 at 6:26 am
Is there any easy way to determine if a hotfix requires the active node or includes desktop tools?
Thanks,
Jen
March 24, 2009 at 7:16 am
Mohit (3/23/2009)
When applying hot fix to active node SQL Server automatically applies to passive node (node defined as passive node for the instance you are patching) Only time you have to run the hot fix on the passive node is when there are desktop tools and such involved as they do not get patched over network.Thanks.
Mohit.
Mohit,
I believe the part where you say it only needs to be applied once is not true for a Veritas cluster. Sql server 2005 does not recognize it as a clustered environment.
We generally just apply hotfixes to the passive nodes. But, there are certain hotfixes that require the active node -- those are the ones that cause problems for us.
March 24, 2009 at 7:24 am
sql hotfixes always apply to the instance, not the node
for windows hotfixes we just terminal server into the passive node and run WU. or if you have a WSUS server or something else you can just set up a policy to do it
March 24, 2009 at 9:35 am
Agree with 'SQL Noob'.
We tend to failover to passive node (out of hours), switch off the now passive node and then run the patch on the active.
The idea here being that we ensure that at least one node remains un-changed and capable of taking over (should the worst happen). Then we power back on once update is complete (shutting down the other node also prevents inadvertent failover)
A week later we do the same to the other node.
Why failover to start with.... Cause I’m anal and like keeping node 1 as the primary (even though there’s no difference).
Adam Zacks-------------------------------------------Be Nice, Or Leave
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply