October 25, 2018 at 1:33 am
Hi all,
I need your help if I can to check over something, let me explain.
Situation
We have 3 servers (all SQL 2012 – 11.0.5343 - Primary,Secondary1 and Secondary2 ) operating in a fairly simple 2 AG setup, in summary, Primary has 2 user databaseson it, 1 of them is sending data (synchronous commit) to Secondary1. The other database is being sent to Secondary2. Failure over both is manual.
We need to patch these to the highest SQL 2012 level (SP4 + Security hot fix) – 11.0.7462.6.
Patching AG servers always makes me nervous and this being a 2012 one even more so. So I wanted to share my plan on this and ask you all what you think, I built up the plan based on Microsoft’s article.
Plan of action
1. Suspend the website which allows users to work with the database(we are fine with the downtime).
2.Backup the databases involved in the AGs (system databasesand the 2 user ones).
3.Upgrade both secondary replica servers to the SP4 and theHF.
4.Wait until synchronization state is SYNCHRONIZED for bothAGs.
5.Fail over both the AG to their secondary replica.
6.Upgrade primary replica server to the SP4 and the HF.
7.Wait until synchronization state is SYNCHRONIZED for bothAGs.
8.Fail over the AG back to the primary site.
9.Test basic functionality of the web site
So what do you think? Have I missed anything out? Any pitfalls you think I should beaware of?
Thanks in advance,
Nic
October 25, 2018 at 4:58 am
I think I'd patch a secondary first, then fail over to it.
October 25, 2018 at 5:04 am
Hi,
Thanks for offering you view, your right, as I have 2 separate AG's on the primary I will do that, I'll patch Secondary 1 first, then failover to it, make sure its all ok and then do the Secondary 2. Then if that's ok do the Primary, that way if the first one has issues I can evaluate how to resolve.
Thanks,
Nic
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply