Solved

SQL 2014 AG in-place upgrade to SQL 2016

Posted on 2016-10-26
2
103 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:justind39
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 40

Accepted Solution

by:
lcohan earned 500 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:justind39
ID: 41869020
thank you for the information
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Many companies are looking to get out of the datacenter business and to services like Microsoft Azure to provide Infrastructure as a Service (IaaS) solutions for legacy client server workloads, rather than continuing to make capital investments in h…
Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

749 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