August 29, 2006 at 6:40 pm
I was just wondering if there are any replication issues that I might run into when migrating a server to new hardware.
My plan was was to restore the master, msdb, distribution, and model databases onto the new hardware, and then detach/attach the replicated user database over to the new server. The new server will take the same name as the current server, and the old server will be renamed.
My main question is will the current replication configuration also be migrated over to the new server after I restore the master, msdb, and distribution databases onto the new server? or will I have to configure the new server for replication and rebuild the publication? My concern with rebuilding the publication is applying the snapshot which takes about 12 hours to reapply if something goes wrong.
If anyone has any advice, it would be greatly appreciated.
August 30, 2006 at 9:54 am
I think your plan should work. That's basically what we did a few months ago.
August 30, 2006 at 2:57 pm
All the replication information is stored in either the db with the data, in distribution db, or in msdb as jobs. Potentially you may have a file share defined for snapshots that would have to be created outside of that. I've got two articles posted that may help, one about moving to a new server that has most of the steps you need, and another that shows how to detach a replicated database (SQL won't let you detach them) which is useful for things like moving your mdf to a different drive without dropping replication.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply