I have a 2008R2 environment that I want to migrate to 2012 for replication. The production servers will remain 2008R2 and I want to replicate using a new 2012 distributor to a new 2012 destination. I have over 30 replication jobs to migrate and want to minimize downtime. My original thought was to add new publications to my existing production servers that would point to the new distribution database. From everything I have been able to find out, that is not an option. So, first question, does anyone know of a way to to this? This would be ideal for the new replication.
Failing that, what is the best way to migrate (with least downtime and best possibility for rollback) from the old replication to the new. My original solution was to leave the old replication untouched until I could verify that the new replication was working properly. If I can't have a publisher that points at more than one distributor, then I don't see how I can do that.
This seems like the only thing is to script out all the existing publications /subscriptions, modify them to point to the new servers with new logins etc. Drop all the old publications /subscriptions en masse and recreate them via the script pointing at the new environment. This seems like a fairly high risk maneuver, with little room for mistake or rollback.
Any ideas? I'm sure I'm not the first to do this.