SQL Serve AAG rolling upgrade .

Question

SQL Serve AAG rolling upgrade .

sakuraime 2,351

suppose there is 2 nodes SQL AG on windows 2012R2, and would like to have a rolling upgrade on OS only . which means there is a period (maybe short) which the cluster contain OS 2012R2 and also 2016 .

AG failover to Windows 2016 Replica , and its it possible to fail over back to windows 2012 R2 replica ? support both manual and also auto ( in case the windows 2016 replica down suddenly )

Seeya Xi-MSFT 16,676 Reputation points

2021-09-08T05:53:00.627+00:00

Hi @sakuraime ,

We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

Best regards,
Seeya

2 answers

Your answer

Seeya Xi-MSFT 16,676 Reputation points

2021-09-08T05:53:00.627+00:00

Hi @sakuraime ,

We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

Best regards,
Seeya

Answer 1

Hi @sakuraime ,

The same OS is not a prerequisite for the realization of an availability group. You need to ensure the same version of the sql instance. Please refer to this article which looks clearer.
https://www.sqlservercentral.com/articles/steps-for-installing-alwayson-availability-groups-sql-2019
Here is the official doc: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-ver15#SystemRequirements

Best regards,
Seeya

If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

sakuraime 2,351 Reputation points

2021-09-08T07:33:15.297+00:00

so can be failover back ? both auto and manual ?

Answer 2

Seeya Xi-MSFT 16,676

Hi @sakuraime ,

Please refer to this doc.
Cluster operating system rolling upgrade: https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
Here is the workflow:

The failover of SQL cluster is based on Windows cluster.
This is an upgrade of the OS. It should be a failover of the windows cluster. It is automatic.

Best regards,
Seeya

sakuraime 2,351 Reputation points

2021-09-09T14:22:28.033+00:00

any doc talks about the failover of a cluster with 1 node 2012 R2 and another node 2016 ??
Seeya Xi-MSFT 16,676 Reputation points

2021-09-10T02:30:59.277+00:00

Hi @sakuraime ,

any doc talks about the failover of a cluster with 1 node 2012 R2 and another node 2016 ??

One prerequisite for Create a failover cluster is
Ensure that all servers that you want to add as cluster nodes are running the same version of Windows Server.

"Stage 1" is the initial state - we start with a Windows Server 2012 R2 cluster. (The nodes are always the same Windows Server in the the initial state)
In "Stage 2", two nodes have been paused, drained, evicted, reformatted, and installed with Windows Server 2016 which not means a cluster contains 1 node 2012 R2 and another node 2016. This is a Intermediate State.

Best regards,
Seeya

Share via

SQL Serve AAG rolling upgrade .

2 answers

Your answer