Replication between 4 servers

Hello,
Currently I have successfully replicated data between 2
servers. The replication is for the most part stable but
does have its "issues" from time to time.I am still in the
process of understanding all situations that could cause
replication to error out.
Anyhow.. Whewww.. I am now in the position that I need to
replicate this data to 2 other servers.
My question is:
If replication occurs between SERVERA, SERVERB SERVERC
SERVERD.Lets say SERVERA replicates to SERVER B and
SERVERC but the replication fails between SERVERA and
SERVERC. Does the replication subscription I set up
between SERVERA and SERVERB also error out?
Sorry this is long winded.
Thanks,
niv
niv,
Not unless the cause of the replication failure between SERVER A and SERVER
C was caused by a network/hardware failure and the subscription on SERVER B
also relies on these resources. As long as the Log Reader and Distribution
agent is running as well as SERVER C and network connectivity is present it
should be fine.
This really is a broad question. I understand that you would like to cover
all possible scenarios and to ask you to be more specific would not be
relevant.
Charles Deaton
"niv" <niv@.hotmail.com> wrote in message
news:1b3c701c44fb3$e2c83b50$a401280a@.phx.gbl...
> Hello,
> Currently I have successfully replicated data between 2
> servers. The replication is for the most part stable but
> does have its "issues" from time to time.I am still in the
> process of understanding all situations that could cause
> replication to error out.
> Anyhow.. Whewww.. I am now in the position that I need to
> replicate this data to 2 other servers.
> My question is:
> If replication occurs between SERVERA, SERVERB SERVERC
> SERVERD.Lets say SERVERA replicates to SERVER B and
> SERVERC but the replication fails between SERVERA and
> SERVERC. Does the replication subscription I set up
> between SERVERA and SERVERB also error out?
> Sorry this is long winded.
> Thanks,
> niv
|||For transactional, there will either be one Distribution Agent per
subscription (an independent agent) or one Distribution Agent per
publication database and subscription database pair (a shared agent). For
merge, each merge subscription has its own Merge Agent that connects to and
updates both the Publisher and the Subscriber. So, as the agents in your
case are independant, a failure in one will not affect the other in a sense
of the replication process. However, as Charles points out, if the error is
a general one to your network then both agents will fail.
HTH,
Paul Ibison