March 8, 2018 at 9:29 am
SQL Server version 11.0.3460.0 and SQL Server version 11.0.3153.0
Hello,
We have an "Always On" setup with Node-1 and Node-2 (with synhronous commit) in our primary location and Node-3 in a DR location (with asynhronous commit). This whole setup is using SQL Server 2012 servers. While Node-1 and Node-2 are on version 11.0.3460.0, Node-3 is on 11.0.3153.0. The service pack update was somehow missed on Node-3, apparently. Now we have a DR exercise coming up tomorrow night and we are expected to make Node-03 primary and leave it there for 3 to 4 days. Our previous attempts to check this setup ran successfully although we only did sanity tests and swung right back to make Node-1 primary. Unfortunately we do not have downtime to apply the patch on Node-3 to bring all SQL server minor versions on par. What risks should I be anticipating with this setup? If anyone else here had similar experience, I would appreciate if you could share it.
Sincerely,
SQLCurious
March 8, 2018 at 10:06 am
SQLCurious - Thursday, March 8, 2018 9:29 AMSQL Server version 11.0.3460.0 and SQL Server version 11.0.3153.0Hello,
We have an "Always On" setup with Node-1 and Node-2 (with synhronous commit) in our primary location and Node-3 in a DR location (with asynhronous commit). This whole setup is using SQL Server 2012 servers. While Node-1 and Node-2 are on version 11.0.3460.0, Node-3 is on 11.0.3153.0. The service pack update was somehow missed on Node-3, apparently. Now we have a DR exercise coming up tomorrow night and we are expected to make Node-03 primary and leave it there for 3 to 4 days. Our previous attempts to check this setup ran successfully although we only did sanity tests and swung right back to make Node-1 primary. Unfortunately we do not have downtime to apply the patch on Node-3 to bring all SQL server minor versions on par. What risks should I be anticipating with this setup? If anyone else here had similar experience, I would appreciate if you could share it.
Sincerely,
SQLCurious
You had time to apply to node 1 and 2, but not node 3??
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 8, 2018 at 10:11 am
I have to agree with Perry. I would NOT risk using the results of this DR exercise to make any kind of business decision, even if the result is successful, without first upgrading Node 3 to the same patch level as nodes 1 and 2. If you do proceed, and I was a manager above you, I'd want the DR exercise re-run after the Node 3 upgrade.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 30, 2018 at 5:16 pm
Perry & sgmunson,
This was done by another groups which apparently missed it out. Thankfully our DR drill was postponed by a week, so we had enough time to bring node-3 on par with the other nodes.
SQLCurious
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply