Replication Doesnt Work after Manual Failover

  • I have the following replication setup in my PROD Servers.

    ServerA -> ServerB -> ServerC

    ServerA is the Publisher

    ServerB is the Distributor. Push Subscription is used.

    ServerC is the subscriber

    Also, there is a Asynchronous Mirroring Setup between Server A & ServerD for the same database without a witness.

    I have also given the -PublisherFailoverPartner parameter to define ServerA and ServerD as publishers for ServerB

    Now when i manually stop the SQL services on ServerA, and force a service on ServerD, and if i update few rows on Published table on ServerD, the rows did not reflect on the Subscriber - ServerC.

    It reflects only when i bring the Principal up and Resume the mirroring session again.

    Why is this so? Please help...

  • Is your problem resolved now?

    By Aravinth Manogaran

  • Server D is not configured as a Publisher in your replication scheme, is it? If not, then the behavior you described makes sense to me. Only Server A is a Publisher.

    Steve

  • Ramkumar,

    I may have misunderstood your description of your system configuration. Since you have set the -PublisherFailoverPartner parameter, that sort of sounds like you have Server D configured to be a publisher.

    Did you follow the steps in BOL for using replication with database mirroring? See http://msdn.microsoft.com/en-US/library/ms151799(v=SQL.90).aspx. It looks like there are a lot of detailed steps that need to be followed. It would be easy to overlook one.

    Steve

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

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