The Distributor is on the Publisher. No error during the
actual restores. Its just the whole box still isnt
configure for replication. I still need to go through the
whole "config pub and dist" wizard. It wants to create a
whole new distribution db and ignore the existing one. And
to top it off, I cant drop the distibution db or the
replication user db because they are being used for
replication. I have to uninstall/ reinstall sql to do that.
[quoted text, click to view] >-----Original Message-----
>Is your distribution db on the subscriber? What error did
you get when
>restoring dist db?
>
>
>Richard
>"chris" <chris@fin2000.com> wrote in message
>news:039d01c356cb$90c05720$a301280a@phx.gbl...
>> sql2k sp3
>> I was wondering if you could point me to a good white
>> paper or the like on log shipping a replicated db and
>> then "failing over" to the warm standby box while
>> retaining all the replication settings? According to
BOL
>> I will also need to be backing up the distribution db.
>> Which is fine. But when I try the whole fail over
>> processs, i.e. restore the distributor then the user
db, I
>> have problems.
>>
>> Thanks in advance.
>> Chris
>
>
>.
Chris,
When you switch over to secondary server, did you rename it to the old
primary server's name? The replication still looks for the old name. I guess
it thinks the standby server as a new server so you have to repeat the
replication configuration. If it has the same name, things should run OK.
Worse come to worse, you could script out the replication and automate the
process as part of the take over.
Richard
[quoted text, click to view] "chris" <chris@fin2000.com> wrote in message
news:051a01c356db$96625880$a301280a@phx.gbl...
> The Distributor is on the Publisher. No error during the
> actual restores. Its just the whole box still isnt
> configure for replication. I still need to go through the
> whole "config pub and dist" wizard. It wants to create a
> whole new distribution db and ignore the existing one. And
> to top it off, I cant drop the distibution db or the
> replication user db because they are being used for
> replication. I have to uninstall/ reinstall sql to do that.
>
>
>
> >-----Original Message-----
> >Is your distribution db on the subscriber? What error did
> you get when
> >restoring dist db?
> >
> >
> >Richard
> >"chris" <chris@fin2000.com> wrote in message
> >news:039d01c356cb$90c05720$a301280a@phx.gbl...
> >> sql2k sp3
> >> I was wondering if you could point me to a good white
> >> paper or the like on log shipping a replicated db and
> >> then "failing over" to the warm standby box while
> >> retaining all the replication settings? According to
> BOL
> >> I will also need to be backing up the distribution db.
> >> Which is fine. But when I try the whole fail over
> >> processs, i.e. restore the distributor then the user
> db, I
> >> have problems.
> >>
> >> Thanks in advance.
> >> Chris
> >
> >
> >.
> >
