登录
 
主页技术资源库学习下载支持社区论坛
IT 专业人士的资源 >
> 
> 
Using transactional replication with an AlwaysOn instance failover cluster.

Answered Using transactional replication with an AlwaysOn instance failover cluster.

  • 2012年4月11日 16:43
     
     
    登录进行投票
    0

    Guidance needed on this one please. If anyone has any suggestions or comments to help alleviate a problem we have.

    We have a two node data AlwaysOn failover cluster that has been working seamlessly. We are able to fully utilize the new AlwaysOn technology and failover between the two nodes rather quickly. We are trying now to implement transactional replication from these two data nodes to child nodes and allow for the transactional publication to failover seamlessly as well. The problem that seems to keep coming up is that the two data nodes need to act as a distributor and published to the child nodes and have this failover without any user intervention. Is this possible to get setup in any fashion where we could run a redirection SP or use powershell or something similar to script the redirection of the publication after failover occurs?

    We have tried to implement the approach outlined here, but it says that the distributor cannot be in the availability group. http://msdn.microsoft.com/en-us/library/hh710046.aspx  -- We need the two parent nodes in the failover group to be the distributor and publisher for the publication. 

    The environment is setup like this:
    Data1 (primary node in Data cluster)
    Data2 (secondary node in Data cluster)

    |  Transactional publication

    Child node1
    Child node2
    Child node3
    Child node4

    We have been able to get this working from one of the nodes but after failover it will not process the replication tasks. I have also tried to setup two individual publications not tied to the failover on each server, but when trying to setup the second publication it tells me the distribution is not setup properly. Any help or advice on this is greatly appreciated.

     

全部回复

  • 2012年4月11日 21:04
    版主
     
     已答复
    登录进行投票
    0
    I'm afraid what you're trying to do is not supported.  The publisher instances must share a common distributor (remote distributor) which cannot be host for any of the replicas of the availability group.  I believe you will need to do this using a remote distributor.

    Brandon Williams (blog | linkedin)

     
  • 2012年4月16日 14:13
     
     
    登录进行投票
    0

    Brandon,

    I appreciate the reply and the insight to the issue. Is there any type of work around that you could think of if it wasn't possible to add a remote distributor? Our server operations group is happy with how the fail over is working between the two Data server nodes with AlwaysOn resources and are very hesitant to have to add a third server into the mix just to be a distributor node only. Let me know if there is anything you can think of that could accomplish this. Thanks again.

     
  • 2012年4月16日 14:16
    版主
     
     已答复
    登录进行投票
    0
    No, Brandon is correct you will be unable to add the distributor to the availability group as replication needs a hard-coded unchanging publisher name UNLESS you are using a mirroring topology or AlwaysON with a remote distributor.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941