Prev: Basic replication question
Next: Reintilize replication via a T-SQL script or command
From: Siz on 22 Mar 2010 14:25
Hi Paul,

Thanks for the response. It should all work in principal and i did not
change the job names. This is all a bit flakey for me and you could say whats
the point in backing up the Distributor in the case of a full server issue.
There should be documentation out ther on how to do a DR for your Dist
database but I can find any.

I am going to stick to a more tried and tested method. Going to get downtime
agreed, quiesce the DB, drop the publications and recreate using a new
distributor and specify that the data already exists so as not to push out
the snapshot (its 4TB!)

Regards
Siz

"Paul Ibison" wrote:

> The only time I have done a complete migration like this is to copy the
> database files. This can be done when the sql server services are stopped.
> if the 2nd computer is named the same as the original hostname this works
> fine. You'll have to isolate the computer on the network to prevent a naming
> conflict while doing this.
> This method worked fine but in principle what you did shold be identical. Am
> wondering if the problem lies in tempdb. What happens if you restart the sql
> server service?
> One final point is the job names - have you changed them? This'll mean that
> the agents are not visible in replication monitor (the job definitions that
> is).
> Cheers,
> Paul Ibison
>
 | 
Pages: 1
Prev: Basic replication question
Next: Reintilize replication via a T-SQL script or command