Trans replication with remote distributor, publisher upgrade question.

  • Hello there, I'm after a bit of advice.

    We have a 2K5SP4 publisher database with a 2K5SP4 remote distributor and over 30 transactional/one-way subscribers (push) with SQL 2008R2. We have a requirement to move the publisher DB to a better server. The system is a 24/7 customer-facing booking engine, so we need to keep downtime to a minimum. Obviously I want to avoid having to reinitialize all the subscribers if possible as it takes a good 24 hours plus.

    I've seen guides on moving single-server publishers, and moving remote distributors, but nothing specifically for moving the publisher only in a remote-distributor setup.

    SQL version will be the same-2K5 SP4, but the OS is Win2003R2 Ent on the old server and Win2008R2 Ent on the new.

    In a nutshell my plan was:

    Shut down distributor

    Backup master, msdb, dist and published database from SERVER-A (Publisher)- distribution database exists on the distributor

    Shut down SERVER-A- that's my DR box.

    Rename SERVER-B to SERVER-A, join to AD, reboot

    Run scripts to rename SQL instance on SERVER-B to SERVER-A

    Restore master, msdb, dist and publisher database (with replication)

    Turn on distributor

    Stop holding breath

    I'm building a test environment now, but if you've got any suggestions or can see anything obviously wrong, please let me know!

    Much appreciated,

    Corin.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply