Re: restore the replication system

From: Hilary Cotter (hilaryk_at_att.net)
Date: 08/09/04 

Date: Mon, 9 Aug 2004 08:11:51 -0400

Paul, the sync with backup option is fairly useless unless you are shipping
the transaction logs to a standby server.

The sequence to get this to work is

1) use the sync with backup option on your publication database and possibly
your distribution database
2) restore the msdb, publication database, and distribution database backups
on the standby server with the keep_replication switch.
3) then ship the publication and distribution databases tlogs and without
the keep_replication switch.
4) when the publisher goes offline you rename the standby server with the
name of the original publisher, and then do a sp_replrestart,
and -skiperrors switch.

In the case of this user you can't really use any of these options as they
have not been shipping the database. With a new master database, the user
probably does not have any of the subscribers listed as remote servers and
restoring or attaching any databases will be highly problematic.

The user is best to drop all replication and create publications and
subscriptions from scratch as their data is likely out of sync. 

-- 
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:uY4Vt9RfEHA.3916@TK2MSFTNGP11.phx.gbl...
> Wen,
>
> there should be no problem with the merge database restoration, and you
> might want to synchronize with the most upto date subscriber after the
> restore.
>
> As for the transactional, there could be issues. Did the publisher have
the
> sync with backup option set to true? If not, the distribution backup could
> be ahead of the publisher restore. After the restore you will get an error
> from the Log Reader Agent because it will detect that the Distributor is
> ahead of the Publisher. The recommendation is to run sp_replrestart in the
> publication database with no parameters. and ensure that that the
> distribution agent, which could now deliver duplicate rows to Subscribers,
> can continue despite these failures. Choose the -SkipError Distribution
> Agent profile, or you can manually add the -SkipError parameter to the
> runtime parameters of the Distribution Agents and supply the errors you
want
> the Distribution Agents to ignore.
>
> You'll need to use linked servers to fix the inconsistencies, or you could
> of course resort to reinitializing.
>
> HTH,
>
> Paul Ibison
>
>

Relevant Pages

  • Re: Question about restore replication database
    ... Ideally your publication and distribution database would be in lock step by ... using the sync with backup option. ... I got a trouble that I tried to restore a database that has a replication ...
    (microsoft.public.sqlserver.replication)
  • Re: Distribution Agents
    ... entries in MSdistribution_agents in the distribution database. ... Director of Text Mining and Database Strategy ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ... "Hilary Cotter" wrote: ...
    (microsoft.public.sqlserver.replication)
  • Re: restrict design access
    ... on the server & multiple copies of the FE distributed to the various user's ... Your best bet here is to use the server path in the MDB with the linked ... References play no part in splitting a database... ... ready for the next distribution. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Distribution Agents
    ... Does it show up in msdistribution_agents in the distribution database? ... Director of Text Mining and Database Strategy ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ...
    (microsoft.public.sqlserver.replication)
  • Re: Newbie question about db normalization theory: redundant keys OK?
    ... principle of "Distribution Independence". ... that it is a distributed database? ... In what way does it attempt to identify row data based on something other ... then any comparison based upon that identifier is suspect. ...
    (comp.databases.theory)