Re: restore the replication system

From: Wen Chang (WenChang_at_discussions.microsoft.com)
Date: 08/07/04 

Date: Sat, 7 Aug 2004 14:47:01 -0700

Paul.

1. Yes, the servername is the same as the original one. and the
Distribution db
      has been restored.
2. We have transactional and merge replication.

 I will attache back the master and msdb and see if it works.

Thanks for the help.

Wen

"Paul Ibison" wrote:

> Wen,
> provided you also restore the distribution database this may be possible. It
> partly depends on 2 factors:
> firstly, is the server name the same as the original one? If not then the
> recovery strategy won't work and you'll need to start again - recreate the
> publications and initialize.
> If the servername is identical, then it may be possible - have a look in BOL
> for "replication, backup and restore operations".
> The second question is what type of replication are you using? In most cases
> it is ok but I'd mention that if the distribution database's backup has been
> allowed to get ahead of the publisher's backup and you are using
> transactional replication there are likely to be problems.
> Anyway, the first port of call is the BOL reference above, and please post
> back if you have any issues which arise from that.
> Regards,
> Paul Ibison
>
>
>

Relevant Pages

  • Re: Backup Distribution Database
    ... If you are using merge replication, I backup the distribution ... database once and never do so afterwards simply because it doesn't store ... please see the BOL topic on "Synch With Backup". ...
    (microsoft.public.sqlserver.clustering)
  • Re: distribution sync with backup
    ... make sure both publication and distribution are sync ... log backup publication. ... log backup publication again to re-initiate replication. ...
    (microsoft.public.sqlserver.replication)
  • Re: replication stops truncating log with option SyncWithBackup
    ... both publisher db and distribution db are on full ... backup very 15 minutes with distribution db has setting "sync with ... today it suddenly stops truncate log on publisher side and backup log ... pending replication. ...
    (microsoft.public.sqlserver.replication)
  • RE: MSmerge_history - Production Issue
    ... You should also be able to delete the merge history beyond the retention ... running continuous Merge replication each with 1 updating subscriber. ... Distribution DB properties are set as follows: ...
    (microsoft.public.sqlserver.replication)
  • Re: replicated commands not executed on the subscriber side?
    ... Unlike the replication procedure when changes made at Subscriber, ... Distribution Agent. ... In our case, when running following the distributed transaction, the ...
    (microsoft.public.sqlserver.replication)