Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

SQL 2014 AG in-place upgrade to SQL 2016

Posted on 2016-10-26
2
Medium Priority
?
200 Views
Last Modified: 2016-11-01
Couple of questions regarding this topic.  Setup that I have is 4 nodes in Hyper-V.  2 same location and the others in different datacenters.  We use the systems databases for all logins.  So will need to migrate them as well.  

1.  When doing an in-place upgrade on an AG what is the rollback?  
2.  When manually failing over after the 3 secondary nodes are upgraded what happens?  
3.  Does it failover instantly or does it take it offline and upgrade?
0
Comment
Question by:Justin Alcorta
2 Comments
 
LVL 40

Accepted Solution

by:
lcohan earned 2000 total points
ID: 41868939
Which of the two availability modes listed below are you using?

<<
Asynchronous-commit mode. This availability mode is a disaster-recovery solution that works well when the availability replicas are distributed over considerable distances.

Synchronous-commit mode. This availability mode emphasizes high availability and data protection over performance, at the cost of increased transaction latency. A given availability group can support up to three synchronous-commit availability replicas, including the current primary replica.
>>


The full upgrade guide is posted here https://msdn.microsoft.com/en-us/library/dn178483.aspx however these are few answers to your questions:


1. When doing an in-place upgrade on an AG what is the rollback?  
You can't really undo an in-place upgrade for single SQL instance alone never mind a full AG with 4 nodes so you would have to un-install everything and then restore your databases from a backup OR...image everything and snapshot storage but you will need to test this rollback scenario in order to rely on it SO...as they say here https://msdn.microsoft.com/en-us/library/dn178483.aspx 
<<â—¦Protect your data by performing a full database backup on every availability database>>


2. When manually failing over after the 3 secondary nodes are upgraded what happens?  
Not sure what you are talking about here but considering you have 4 nodes and didn't mentioned anything yet about the "last" one please note that in a "Rolling Upgrade" scenario you will "Always upgrade the remote secondary replica instances first, then local secondary replica instances next, and the primary replica instance last."

3. Does it failover instantly or does it take it offline and upgrade? -- it will "upgrade" indeed each SQL database on that instance same as you would do a backup/restore from old version to newer one so please test on largest database to estimate needed "downtime"

More about the topic is described here:
https://www.brentozar.com/archive/2015/02/patching-sql-server-availability-groups/
0
 
LVL 1

Author Closing Comment

by:Justin Alcorta
ID: 41869020
thank you for the information
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question