After Server2 was renamed to Server1 and Server1 decommissioned, replication is not working on the new Server1 due to the renaming issue. I can afford to re do replication from ground up on Server1 but cannot reinstall SQL Server 2005 and start from scratch since the server is already in production.
How can I resolve this issue? What is the right approach to take for the scenario described above?
Its unclear to me what state the new server 1 is in now. To get this to work you should have restored the master, msdb, distirbution, and publication databases, and then the transaction logs of the publication databases, followed by the tail of the publication database restored with the keep_replication switch. These should have been restored to a SQL 2000 server, the new SQL 2000 server should br renamed Server1 and restarted. Then run the sp_replrestart command, and run with the continue on data consistency error profile until the errors are cleared.
Then upgrade your publisher to SQL 2005.
If publications exist in Server1, attempt to script them out and then drop the publications and recreate them with the script and then redeploy your subcribers.
No comments:
Post a Comment