Migrating a SQL Server 2014 AG to a new 2017 AG
4
votes
1
answer
167
views
Our current production server runs on SQL Server 2014 AlwaysOn AG. We are planning to upgrade it to SQL Server 2017 AlwaysOn.
Due to the configuration issues with the present cluster, we can not use the existing cluster.
The production server has 52 databases with a total size of 2 TB. The databases servers an online system, so minimum downtime is our core requirement.
Our initial plan is to go for a side by side approach.
1. Provision 3 SQL Server 2017
2. Create new cluster
3. Logs from the existing 2014 AG Primary server to all the servers in the new 2017 group.
On the switchover day,
1. Disconnect all applications from the existing server.
2. Do a final logshipping.
3. Apply logs to all servers in the new group WITH NORECOVERY, except WITH RECOVERY on Primary_new
4. Create AG and add all database to AG
5. Change all applications to point to the new cluster.
6. Shutdown old cluster.
Is this a good approach? Are there any other approaches?
If I am missing anything, please guide me.
Thanks.
Our initial plan is to go for a side by side approach.
1. Provision 3 SQL Server 2017
2. Create new cluster
3. Logs from the existing 2014 AG Primary server to all the servers in the new 2017 group.
On the switchover day,
1. Disconnect all applications from the existing server.
2. Do a final logshipping.
3. Apply logs to all servers in the new group WITH NORECOVERY, except WITH RECOVERY on Primary_new
4. Create AG and add all database to AG
5. Change all applications to point to the new cluster.
6. Shutdown old cluster.
Is this a good approach? Are there any other approaches?
If I am missing anything, please guide me.
Thanks.
Asked by user1716729
(693 rep)
Dec 27, 2018, 05:48 PM
Last activity: Jul 18, 2025, 05:03 PM
Last activity: Jul 18, 2025, 05:03 PM