May 22, 2013 at 3:08 am
Hi all
I´me new to the DBA role and this weekend we are having our first "maintenance weekend" in a while, where we apply windows security patches and such.
we have 3 clusters running active/active configurations.
normally, i move the sql server instances from server A and then apply the patches, reboot the server and repeat the process for server B, C and D.
i was thinking... what if i apply the patches on all servers at the same time and then juggle the instances only to perform the rebooting procedure, would that "hurt" SQL server?
who do you guys do this? and how often ?
is there a way to script this to do it automatically?
any and all thoughts on the topic is much appreciated!
May 22, 2013 at 3:20 am
It is better to apply patches one by one. In this way you can minimize server downtime. Otherwise all your 3 servers will be down for the process.It is not very clear what type of patches u need to execute in the servers. Is it some kind of maintenance jobs like updating statistics, purging tables, etc.
Can you please elaborate more on this
May 22, 2013 at 4:47 am
im sorry if i was unclear.
4 servers in a cluster
we need to apply microsoft security updates from our WSUS server.
the way i do it now:
move all clustered instances from server A
install WSUS updates and reboot server A
move all clustered instances from server B
install WSUS updates and reboot server B
move all clustered instances from server C
install WSUS updates and reboot server C
move all clustered instances from server D
install WSUS updates and reboot server D
the way i was thinking about
move all clustered instances from server A
install WSUS updates and reboot server A
while server A are installing i initiate:
install WSUS updates on server B
AND
install WSUS updates on server C
AND
install WSUS updates on server D
WHEN server A is up, move all instances from server B and reboot B
WHEN server B is up, move all instances from server C and reboot C
WHEN server C is up, move all instances from server D and reboot D
in essence, i install the windows updates on all servers at the same time, reducing the overall time from start to finish
the "problem" is that there will be instances running on servers B,C and D while the security patches are applied
the question is, will this have a negative impact on SQL Server?
May 23, 2013 at 12:02 am
Below are some best practise documents which u can refer.Hope it helps
http://technet.microsoft.com/en-us/library/cc750077.aspx
http://technet.microsoft.com/en-us/library/cc966456.aspx
But as per ur requirement since upgrade will take place in my view(i am not sure) it will definitely impact SQL server instances. So its better to move instances first and then do upgrade
May 23, 2013 at 2:30 am
If the cluster node has enough capacity (mem, CPU) you could move all SQL-instances to one node.
1. Move all SQL instances to node A.
2. Install patches on nodes B, C and D simultaneous and reboot them.
3. Distribute the SQL instances to their preferred patched nodes (B, C and D) and also move all SQL instances from node A to one of the three patched nodes.
4. Patch and reboot node A.
5. Move all SQL instances with preferred node A back to this node.
With above steps you only require two movements of each SQL instance and only require two patch-batches.
May 23, 2013 at 2:33 am
why didnt i think of that? =)
probably because all instances are not installed on all the clustered nodes!
its on my "to do" list though...
thanks!
May 23, 2013 at 2:38 am
Instead of patching first three nodes and second one node, you could also patch first two nodes and second other two nodes. Perhaps you could allready implement this without installing the instances on all nodes.
May 23, 2013 at 2:40 am
i will look into that, thanks!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply