Is restore of a republishing database possible from one of its subscribers in merge replic

Hi,
I've a republishing database (using merge replication) which has more than 1
subscriber. The database has gone into suspect mode and there is a problem
with 2 tables. I've all the data on its subscribers. However, each
subscriber also has some changes which have not been sent to the publisher
after it has gone to Suspect mode. Unfortunately, we don't have a backup of
the republishing database.
Is it possible to backup the database on one of the subscribers and restore
it on the publisher with the keep_replication switch? If yes, will it lead
to some data loss with the chages that remain pending at the subscribers and
have not been transferred to the republisher yet? If I can't restore using
one of the subscribers, do I have other options?
The two tables that have gone bad in the republishing database have the data
on the subscribers.
Regards,
Rajnish Gupta
You can do this, but there are some caveats - review
http://msdn2.microsoft.com/en-us/library/aa237097(sql.80).aspx - for SQL
2000 and for SQL 2005 follow:
http://msdn2.microsoft.com/en-us/library/ms152497.aspx
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
"Rajnish Gupta" <guptarajnish@.hotmail.com> wrote in message
news:OfMWOHiZHHA.4420@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I've a republishing database (using merge replication) which has more than
> 1 subscriber. The database has gone into suspect mode and there is a
> problem with 2 tables. I've all the data on its subscribers. However, each
> subscriber also has some changes which have not been sent to the publisher
> after it has gone to Suspect mode. Unfortunately, we don't have a backup
> of the republishing database.
> Is it possible to backup the database on one of the subscribers and
> restore it on the publisher with the keep_replication switch? If yes, will
> it lead to some data loss with the chages that remain pending at the
> subscribers and have not been transferred to the republisher yet? If I
> can't restore using one of the subscribers, do I have other options?
> The two tables that have gone bad in the republishing database have the
> data on the subscribers.
> Regards,
> Rajnish Gupta
>
|||Dear Hilary,
Thanks for your quick response. I'll go through the link for SQL Server 2005
as this is what I'm using.
Do you recommend recovering the database only or the log file also?
Regards,
Rajnish Gupta
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23iEGb6iZHHA.4000@.TK2MSFTNGP02.phx.gbl...
> You can do this, but there are some caveats - review
> http://msdn2.microsoft.com/en-us/library/aa237097(sql.80).aspx - for SQL
> 2000 and for SQL 2005 follow:
> http://msdn2.microsoft.com/en-us/library/ms152497.aspx
> --
> 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
>
> "Rajnish Gupta" <guptarajnish@.hotmail.com> wrote in message
> news:OfMWOHiZHHA.4420@.TK2MSFTNGP02.phx.gbl...
>
|||both.
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
"Rajnish Gupta" <guptarajnish@.hotmail.com> wrote in message
news:OPZTkNzZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> Dear Hilary,
> Thanks for your quick response. I'll go through the link for SQL Server
> 2005 as this is what I'm using.
> Do you recommend recovering the database only or the log file also?
> Regards,
> Rajnish Gupta
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23iEGb6iZHHA.4000@.TK2MSFTNGP02.phx.gbl...
>
|||Dear Hilary,
I'll try the restore tomorrow. It will be a lighter day on the database.
I've gone through the SQL Server 2005 link and I understand that I just have
to restore the database (by taking any of the subscriber's backup) with the
"Keep Replication" switch. After restore the Publisher will automatically
receive updates from other subscribers. The other subscribers are configured
for pull subscriptions. The other subscribers will also receive the data
propagated to the publisher by each of them. So all of them will be
synchronised with the data each of them have been holding up while the
publisher has been down.
I hope I haven't missed anything.
Regards,
Rajnish Gupta
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23uUfJu9ZHHA.5080@.TK2MSFTNGP02.phx.gbl...
> both.
> --
> 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
>
> "Rajnish Gupta" <guptarajnish@.hotmail.com> wrote in message
> news:OPZTkNzZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>
|||I think you will have to recreate the jobs unless they are all pull. Make
sure you script everything out before you do the restore.
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
"Rajnish Gupta" <guptarajnish@.hotmail.com> wrote in message
news:%2350myBlaHHA.4520@.TK2MSFTNGP06.phx.gbl...
> Dear Hilary,
> I'll try the restore tomorrow. It will be a lighter day on the database.
> I've gone through the SQL Server 2005 link and I understand that I just
> have to restore the database (by taking any of the subscriber's backup)
> with the "Keep Replication" switch. After restore the Publisher will
> automatically receive updates from other subscribers. The other
> subscribers are configured for pull subscriptions. The other subscribers
> will also receive the data propagated to the publisher by each of them. So
> all of them will be synchronised with the data each of them have been
> holding up while the publisher has been down.
> I hope I haven't missed anything.
> Regards,
> Rajnish Gupta
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23uUfJu9ZHHA.5080@.TK2MSFTNGP02.phx.gbl...
>