question

CristianMitan-4805 avatar image
0 Votes"
CristianMitan-4805 asked ·

Migrate from SQL Server 2014 Failover Cluster to 2019 Availability Group and rollback plan

Hi,
we have a 2 node SQL Server 2014 failover cluster with 2 SQL Server instances and about 100 databases to be migrated to an availability Group 2019. What is the faster way to do that considering that we have one weekend for any instance? What's the best rollback strategy considering that restore from a recent version to an older one is not possible? Any idea?

thanks

sql-server-migration
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

Cathyji-msft avatar image
0 Votes"
Cathyji-msft answered ·

Hi @CristianMitan-4805,

we have a 2 node SQL Server 2014 failover cluster with 2 SQL Server instances and about 100 databases to be migrated to an availability Group 2019.

What did you real mean? SQL server 2014 failover cluster instance is a instance level HA. SQL server 2019 availability group is a database level HA. They are different. Please refer to the blog Always on Availability Groups vs Always on Failover Cluster Instances to get more information.

Or if you have SQL server 2014 AG and want to upgrade AG replica instance from SQL 2014 to SQL2019? Suggest you rolling upgrade for AG replica instance. Refer to Rolling Upgrade Process to get detail steps.

Or if your AG contains failover cluster instance (FCI) nodes, you should upgrade the inactive nodes before you upgrade the active nodes. Refer to AG with Failover Cluster Instance Nodes to get detail upgradation steps.

If I misunderstood your question, please let me know. And please describe your question more clearly to make us better understood this question .


If the response is helpful, please click "Accept Answer" and upvote it, thank you.
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.


· 2 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


Thanks Cathyji

we have a FCI 2014, 2 servers with shared disks, and trying to migrate to an Availability Group 2019 a completely different architecture. My main issue is the rollback in case something goes wrong because from newer version to older one it's not possible to use restore db or even Log shipping.

thank again
Cristian

0 Votes 0 ·
Cathyji-msft avatar image Cathyji-msft CristianMitan-4805 ·

Hi @CristianMitan-4805,

Suggest you read the reply that i offered above again. We can’t migrate SQL FCI to SQL AG. Did you mean, you want to upgrade SQL 2014 FCI to SQL 2019 FCI, and the AG databases are part in FCI( AG replica is one node of SQL FCI)? If so, suggest you read the document AG with Failover Cluster Instance Nodes that mentioned above.

For the question about rollback when upgrading failed. Don’t worry about that, we always upgrade inactive replica firstly, the active node is well. If upgradation on one node failed, you still have another node that works well.


0 Votes 0 ·