restore to new hardware

We wil be upgrading all of our sql servers to new hardware and from Windows
2000 to 2003. The servers are in a merge replication topology.
We hope to keep the server names the same.
It would be an extreme hardship to drop the publications and recreate them.
Given these parameters, what is the best approach?
Do one last sync. Take the publisher offline, back up all databases to tape,
restore on the new server. Reboot. It should come up automagically.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"CHeineken" <CHeineken@.discussions.microsoft.com> wrote in message
news:AA8B3EBA-C4C7-468B-AB23-27CFC725DB48@.microsoft.com...
> We wil be upgrading all of our sql servers to new hardware and from
> Windows
> 2000 to 2003. The servers are in a merge replication topology.
> We hope to keep the server names the same.
> It would be an extreme hardship to drop the publications and recreate
> them.
> Given these parameters, what is the best approach?
>
|||Just to be clear...
When you take the publisher offline, do you mean stop all agents?
When restoring to new server, here is the plan:
Install SQLServer with same service packs and hotfixes as default instance
on server with the same name as original.
Start SQLServer in single user mode.
Restore master and msdb
Start SQLServer in normal mode.
Restore Distribution, model, tempdb and user databases.
Is this correct? Am I missing anything?
"Hilary Cotter" wrote:

> Do one last sync. Take the publisher offline, back up all databases to tape,
> restore on the new server. Reboot. It should come up automagically.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "CHeineken" <CHeineken@.discussions.microsoft.com> wrote in message
> news:AA8B3EBA-C4C7-468B-AB23-27CFC725DB48@.microsoft.com...
>
>
|||Forget what I said about restoring the tempdb...brain fart.
"CHeineken" wrote:
[vbcol=seagreen]
> Just to be clear...
> When you take the publisher offline, do you mean stop all agents?
> When restoring to new server, here is the plan:
> Install SQLServer with same service packs and hotfixes as default instance
> on server with the same name as original.
> Start SQLServer in single user mode.
> Restore master and msdb
> Start SQLServer in normal mode.
> Restore Distribution, model, tempdb and user databases.
> Is this correct? Am I missing anything?
> "Hilary Cotter" wrote:
|||Yes, run the agents one last time until they stop or report no replicated
data. Then follow your steps and in the final restore of the user database
use the keep_replication switch.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"CHeineken" <CHeineken@.discussions.microsoft.com> wrote in message
news:81899ABF-321B-42E2-9370-5C7143B02E63@.microsoft.com...[vbcol=seagreen]
> Just to be clear...
> When you take the publisher offline, do you mean stop all agents?
> When restoring to new server, here is the plan:
> Install SQLServer with same service packs and hotfixes as default instance
> on server with the same name as original.
> Start SQLServer in single user mode.
> Restore master and msdb
> Start SQLServer in normal mode.
> Restore Distribution, model, tempdb and user databases.
> Is this correct? Am I missing anything?
> "Hilary Cotter" wrote: