"Michael" <docware@hotmail.com> wrote in message
news:dc64e00c.0312310440.2cb1adbb@posting.google.com...
> Hi,
>
> We run a merge replication using SQL Server 2000.
> In order to be prepared for crash situations, I am in the middle of
> testing several rescue scenarios.
>
> Presently I simulate a corrupted master database on the publisher. Due
> to the corrupted master db SQL Server is unable to start. I have
> available backups of all system and user databases. This is what I
> did:
>
> - create a new master db using the rebuild-master-db tool
> -> now SQL Server is able to start
> - restore backed up master db
> - restore backed up msdb, model, distribution dbs
> - restore the published user db
> -> The publication is now visible in Enterprise Manager tree. But when
> I want to open the publication properties, SQL Server tells me "Error
> 20026: The publication xyz does not exist".
>
> What am I doing wrong. I read the online documentation (replication /
> backup and restore of replicated databases / strategies for backup and
> restore of replicated databases). From what I read I think it should
> be possible to restore a replication this way without the need to
> recreate the publication and reinitialize all subscribers (we have
> about 10 subscribers temporarily connected to our server via low
> bandwith and the replicated database has a size of 150 MB so
> reinitialization is difficult).
>
> Thanks for help
>
> Michael

"Hilary Cotter" <hilaryk@att.net> wrote in message news:<#JqxCD7zDHA.1996@TK2MSFTNGP12.phx.gbl>...

> restore the published db with the keep replication switch.