Migration path for Server 2012 (non-R2) SQL Failover Cluster

Question

Migration path for Server 2012 (non-R2) SQL Failover Cluster

Eddy 1

We have a 2 node SQL Server cluster running on Windows Server 2012 (non-R2). What is the optimal path to migrate the cluster from 2012 (non-R2) to 2016 or 2019? Should we just create 2 new 2016 or 2019 VMs and create a new cluster? Should we create a 2012 R2 VM and create a new cluster and then evict one of the existing nodes and perform an in place upgrade to 2012 R2?

Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-09T02:10:12.413+00:00

Hi,

Do you have any further question?

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-15T05:02:33.307+00:00

Hi,

May I know if your issue is resolved or not?

It will be much appreciated and encouraged if you could click "Accept Answer" and upvote the helpful reply.

Thanks a lot.

Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-09T02:10:12.413+00:00

Hi,

Do you have any further question?

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-15T05:02:33.307+00:00

Hi,

May I know if your issue is resolved or not?

It will be much appreciated and encouraged if you could click "Accept Answer" and upvote the helpful reply.

Thanks a lot.

Answer 1

Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Microsoft Vendor

Hi,

There are ways to migrate your Server 2012 SQL failover cluster to 2016 or 2019.

The first one is to migrate it to a new cluster by creating a parallel SQL Server environment on a different Windows Cluster with Windows Server 2016 or 2019. That means, you will need to create 2 new 2016 or 2019 VMs and create a new cluster. The impact is that there will be some downtime.
Please refer to below articles for details.
https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/upgrade-sql-server-failover-cluster-instance-2008-2012?view=sql-server-ver15#scenario-2-windows-clusters-with-sql-server-failover-cluster-instances-fcis

The second one is to do in-place migration to Server 2012 R2 first and then do rolling upgrade to 2016 or 2019.
Please read below articles for detailed steps.
In-Place Migration for a Two-Node Cluster: Migration to Windows Server 2012 R2
Cluster operating system rolling upgrade

Thanks,

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Eddy Jackson 1 Reputation point

2021-07-08T00:00:32.343+00:00

So, if we want to avoid downtime, we would need to evict the inactive Server 2012 node and do an in-place upgrade of the node to 2012 R2? And essentially hope that the active node doesn't have any service disruptions during either upgrade? Wouldn't it make sense to also setup a 3rd 2012 R2 node to join the cluster during the upgrade process?
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-08T01:53:59.403+00:00

Hi,

we would need to evict the inactive Server 2012 node and do an in-place upgrade of the node to 2012 R2

Yes

And essentially hope that the active node doesn't have any service disruptions during either upgrade?

First node is evicted from the old cluster, the second node in the old cluster will provide service normally. But high availability is lost since there is only one node working.
After the cluster role is migrated to the new cluster with the first node, which has been upgraded to 2012 r2, and you bring the role online on the new cluster, this first node will provide service in the new cluster. Still high availability will be lost during the upgrade for the second node.

Wouldn't it make sense to also setup a 3rd 2012 R2 node to join the cluster during the upgrade process?

I think 2012 and 2012 R2 cannot be compatible in the same cluster. So, if you add the 3rd 2012 r2 node to the new cluster after the first node is upgraded and cluster roles has been migrated and online, it seems you do not need to upgrade the second node in the old cluster since you already had a new 2012 r2 node added to the new cluster.

Thanks,
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,621 Reputation points Microsoft Vendor

2021-07-13T01:47:45.687+00:00

Hi,

May I know if you have any further question?

If no, could you please help to click "Accept Answer" so that others could find the solution to similar questions quickly?
Eddy 1 Reputation point

2022-09-06T18:27:49.187+00:00

Sorry for the delayed response. I do have a follow up question... So, if we evict one node and perform the in-place OS upgrade from 2012 non-R2 to 2012 R2, how then do we transfer the cluster roles from the 2012 non-R2 node to the then upgraded 2012 R2 server that was evicted from the cluster?
Eddy 1 Reputation point

2022-09-14T18:12:29.96+00:00

ElevenYu-MSFT, please advise....

Migration path for Server 2012 (non-R2) SQL Failover Cluster

1 answer

Activity