Post reply

PublisherFailoverPartner limitation?

  • September 28, 2011 at 3:13 pm

    #390504

    Hi all,

    I am not sure if it's me or this is limitation of PublisherFailoverPartner

    i have the following Asynchronous mirroring in my servers.

    ServerA (DistributionCenter1) -> ServerA (DistributionCenter2)

    ServerB (DistributionCenter1) -> ServerB (DistributionCenter2)

    ServerC (DistributionCenter1) -> ServerC (DistributionCenter1)

    Here is transactional replication setup in DistributionCenter1:

    ServerA and ServerB in DistributionCenter1 are the Publishers

    ServerC is the subscriber in DistributionCenter1

    ServerD is the remote Distributor in DistributionCenter1. Push Subscription is used.

    Now when i try to setup -PublisherFailoverPartner parameter to define ServerA and ServerB as a publishers to DistributionCenter2

    by using Distributor property and the logreader agent profile it only accepts one server name for DistributionCenter2.

    It seems like in order to make logreader agents to be failover aware i need to have only one server on DistributionCenter2.

    Has anyone seen this problem before? or maybe it's not a problem?

    Thanks

  • September 30, 2011 at 1:48 am

    #1388711

    I didn't get your question clearly. Is this Mirroring issue or Replication issue?

  • September 30, 2011 at 2:14 am

    #1388724

    This is replication issue

  • October 5, 2011 at 9:06 am

    #1390741

    I think you need 2 log reader agent profiles to do this, so you'll need to create a new 1.. 1 specifying ServerA in DistributionCentre2 as a failover partner, and the other specifying ServerB in DistributionCentre2 as a failover partner.

    You'll then need to change the log reader agent profile on each publication to point to the relevant profile.

    Vultar

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply