重新创建复制:最简单的方法? [英] Recreate Replication: easiest way?

查看:47
本文介绍了重新创建复制:最简单的方法?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有两个节点,节点1是发布者/分发者,节点2是订阅者。

I have two nodes, Node 1 is publisher/distributor, Node 2 is a subscriber.

他们使用彼此之间的AD域帐户进行身份验证

They authenticate using an AD domain account between one another

最近发生了灾难性故障,导致我们从用于此身份验证的AD帐户之前恢复Active Directory控制器。

Recently a catastrophic failure caused us to recover an Active Directory controller from prior to the date that the AD account used for this authentication existed.

现在,某些存储过程已经存在从节点2提取数据的节点1失败:

Now, certain stored procedures on Node 1 which pull data from Node 2 fail with:

Msg 18456,Level 14,State 1,Line 10

用户'NT AUTHORITY \登录失败ANONYMOUS LOGON'。

Msg 18456, Level 14, State 1, Line 10
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

尝试sp_dropserver导致:

Attempting to sp_dropserver results in:

Msg 20584,Level 16,State 1,过程sp_MSrepl_check_server,第67行[批处理开始行137]
$
无法删除服务器"Node2",因为它在复制时用作远程发布者"Node1"的订阅者。

Msg 20584, Level 16, State 1, Procedure sp_MSrepl_check_server, Line 67 [Batch Start Line 137]
Cannot drop server 'Node2' because it is used as a Subscriber to remote Publisher 'Node1' in replication.

我已使用新的域帐户重新创建了Node2上的登录。如何更新"链接服务器"?登录帐户没有破坏复制?或者,如果我确实需要打破复制,并重新重建它,那么最简单的方法就是在没有丢失任何节点上的数据的情况下获得

I have recreated the Login on Node2 using the new domain account. How can I update the "linked server" login account without breaking replication? Or if I do need to break replication, and rebuild it again, what's the easiest way to go about it without losing data on either node?

非常感谢任何见解。

更新:如果我在使用sql身份验证登录时运行脚本,我发现复制正在运行并且跨服务器查询工作正常。我尝试为SQL Server重新创建自己的域帐户登录,测试我可以在
两台服务器上使用该帐户登录。但是,跨服务器查询仍然无效。

UPDATE: I discovered that replication is working and querying across servers works if I run the script while logged in using sql authentication. I tried recreating my own domain account login for SQL Server, tested that I can log in with that account on both servers. However, querying across servers still doesn't work.

不确定原因。

推荐答案

首先,设置复制时创建的链接服务器没有为数据访问设置,然后测试它们并不总是有效,除非您更改这些链接服务器的配置。您不需要更新链接的服务器。它是在Subscription
或出版物安全设置下完成的。

Firstly the linked servers created when setting up replication are not set for Data Access then testing these are not always work, unless u change configuration of these linked servers. You do not need update linked servers. It is done under Subscription or Publication Security settings.

"现在,节点1上从节点2提取数据的某些存储过程失败,并带有"

你说节点1是发布者?为什么你说Node1从节点2中提取数据?

使用push或pull进行什么复制?

What replication u using push or pull?

如果是push你可以更新订阅安全性并选择在运行分发代理和向订阅者进行身份验证时要使用的其他帐户(如果需要,可以设置SQL身份验证)。如果两个服务器位于同一域中,则只使用SQL Service帐户
运行分发代理。我假设AD已经恢复?

If it is push u can update subscription security and choose different account to be used while running distribution agent and authenticating to subscriber (you can setup SQL auth if needed). If both servers are in same domain just use SQL Service account to run distribution agent. I am assuming AD is back up?





这篇关于重新创建复制:最简单的方法?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆