October 16, 2017 at 8:20 am
Hey all,
I will be moving/upgrading an existing clustered Availability Group from 2014 to 2017 (I believe it would be the exact same procedure as 2016).
Current servers (only primary & secondary) are SQL2014 on Server 2008R2 with about 1.5TB of database files in synchronous mode.
New servers will be on Server 2016 with SQL2017.
What is the best way to move the existing databases with minimal downtime to the new servers and retain existing AG/listener? In theory, I believe you can join the new servers to the old AG and do some wizardry there but the microsoft docs don't seem to tackle this particular scenario.
I'm guessing:
1. Join new SQL2017 servers to old SQL2014 AG.
2. ? Restore databases onto SQL2017
3. ? start with secondary role first, switching it from 2014 to 2017. Then switch primary role from 2014 to 2017 server.
4. Remove 2014 servers
If someone could correct me or outline how best to do this it would be greatly appreciated.
October 17, 2017 at 9:34 am
Has anyone gone through this procedure or have any thoughts?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply