all groups > sql server replication > august 2007 >
You're in the

sql server replication

group:

replication server crashed


replication server crashed Darin
8/27/2007 4:15:46 PM
sql server replication:
One of our customers had their publisher machine crash (harddrives went
down). This is running merge replicaton. The subscribers have continued
operating today.

Their network person "backed up the database". As of right now, I don't
know exactly what was backed up and how.

Can someone point me in the right direction to get the server set back
up for merge, and have what the subscribers did today get replicated
without any issues.

Thanks.

Darin

Re: replication server crashed Hilary Cotter
8/27/2007 10:57:50 PM
I am unsure what state your replication topology is in.

If the database is restored and the master, distribution, and msdb database
are still healthy, the subscribers will fill in missing transactions in the
publisher. If the entire server is restored on new hardware it must have the
same name as the old server, and the master, msdb, publication and
distribution database must be restored as well. You must use the
keep_replication switch while restoring these databases.

If any of these components cannot be restored you have to recreate your
publications and subscriptions, hopefully using scripts you have saved from
the existing topology. Once this is done use sp_addtabletocontents on the
subscriber to push the changes which occurred there to the publisher.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
[quoted text, click to view]

Re: replication server crashed Darin
8/28/2007 12:54:51 PM
So the master and msdb databases weren't backed up.

To use sp_addtablecontents, will that move all data that changed from
the subscriber to the publisher, or will ALL data from the subscriber be
moved? My reason is they have 3 subscribers that have been running and
subscriber 1 data needs to be moved and then 2 be moved, etc.

This is now in crisis mode for them, so any quick information would be
greatly appreciated.

Thanks.

Darin

Re: replication server crashed Darin
8/28/2007 2:18:47 PM
i don't mind setting up replication again (especially since i don't have
a choice), it is just getting the changed data from the subscribers. I
know I can use sp_mergedummyupdate, but that just takes forever.

Darin

Re: replication server crashed Hilary Cotter
8/28/2007 9:24:40 PM
All data will be "moved" but if it conflicts it will not be problematic.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
[quoted text, click to view]

Re: replication server crashed Hilary Cotter
8/28/2007 9:26:50 PM
Job history and job information is stored in the msdb database including
information about the replication jobs. Replication information is stored in
the distribution database and the publication database. You will be able to
recreate the publication information by restoring using the keep_replication
switch or by consulting the system tables in the publication and
distribution databases.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
[quoted text, click to view]

Re: replication server crashed Ekrem_Önsoy
8/28/2007 11:53:17 PM
Hello Darin,


As far as I know, Job and History information are kept in "msdb" database
and all configuration information about replication are stored in "master"
database. So as you can not restore them (because you said you don't have
their backups) it means you lost your replication configuration in the
publisher and as Master Hilary commented in his last message, I think you'll
have to reconfigure replicatication in the publisher over again.

But you better wait for the verdict of the master :)

--
Ekrem Önsoy



[quoted text, click to view]
AddThis Social Bookmark Button