I have a production SQL Server of version 2008 running on a cluster which is proposed to be migrated to a SQL Server 2014 cluster and the end result is to keep server names same.
The end result of renaming the SQL Server has been tried and tested well and is not a problem. However, the server is involved heavily in replication. It acts as a Publisher as well as Subscriber to different other SQL Servers.
If the server names were different, then the replication had to be rebuild using'replication support only' method. However since we are retaining the same name, I would like to hear if there is a better way to create replication other than dropping and re-creating.
One approach that has been occupying my mind is to:
1) Stop and disable all the log-reader agents and distribution agents so that no replication agent tries to hit this server.
2) Copy the master DBs and restore other user DBs to new server
3) Change the names to the existing one(take 2008 one offline)
However, there are few obstacles in this approach:
1) Master DB cannot be restored to a different version so I need to do something to have a copy of 2014 version
2) User databases are large, some around 1 TB so restoring them with fresh copy will not be feasible during 3-4 hours maintenance window.
3) I read that 'preserve replication settings don't work when we restore DBs in 'no-recovery mode'
I hope you can understand what I am trying to achieve. Please share your inputs and suggestions regarding this challenge.