General changes to replication agents to support availability groups After failover, a tracer token cannot be entered by using the Replication Monitor, however a tracer token entered on the new publisher by using Transact-SQL, is visible in Replication Monitor. It may not be redirected to an explicit node.Īfter failover to a secondary replica, Replication Monitor is unable to adjust the name of the publishing instance of SQL Server and will continue to display replication information under the name of the original primary instance of SQL Server. If a published database is a member of an availability group and the publisher is redirected, it must be redirected to an availability group listener name associated with the availability group. Republishing is only supported when transactional replication is combined with Always On availability groups. In an availability group, a secondary database cannot be a publisher.
When the replication agent restarts after failover, the connection will automatically be redirected to the new primary. Established connections through the availability group listener name will fail on failover. These entries redirect the originally configured publisher/database pair, making use of an availability group listener name to connect to the publisher and publishing database. When a published database is aware of Always On availability groups, the distributor that provides agent access to the publishing database is configured with redirected_publishers entries. Overview of replication with availability groups Publisher Redirection Always On availability groups helps provide high availability and other database recovery capabilities. SQL Server Replication, change data capture (CDC), and change tracking (CT) are supported on Always On availability groups.
0 kommentar(er)
