本文介绍了此辅助副本未连接到主副本。连接状态为DISCONNECTED的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

嗨伙计


我遇到了SQL可用性组的问题,我想知道你是否可以帮忙解决问题:


我在2012R2上运行了2个SQL Server。


我已将它们设置为Always on Availability Group,其可用性模式设置为Synchronous Commit,Readable secondary设置为No。


  我认为这一切都运行良好但是当我在Microsoft SQL Management Studio中做了一些不相关的事情时,我注意到辅助服务器的可用性副本状态有一个红叉。然后,我检查了可用性组
仪表板,现在可以在辅助设备下看到:


同步状态:未同步


故障转移准备:数据损失


这个辅助副本是未连接到主副本。连接状态为DISCONNECTED。


此可用性副本上至少有一个可用性数据库具有不健康的数据同步状态。如果这是异步提交可用性副本,则
所有可用性数据库都应处于SYNCHRONIZING状态。如果这是同步提交可用性副本,则所有可用性数据库都应处于SYNCHRONIZED状态。


此可用性数据库的数据同步状态不健康。在异步提交可用性副本上,每个可用性数据库在SYNCHRONIZING状态下应为
。在同步提交副本上,每个可用性数据库都应处于SYNCHRONIZED状态。


我已检查防火墙端口,5022已打开且未被阻止。我还检查了netstat以确认sqlsrvr.exe正在使用5022。我现在开始认为这可能与许可有关。


任何人都可以帮助我指出从哪里出发的正确方向吗?



非常感谢!

解决方案

Hi Guys

I am having an issue with an SQL Availability Group and am wondering if you can lend a hand troubleshooting:

I have 2 SQL Servers on 2017 running on 2012R2.

I have set them up in an Always on Availability Group with Availability mode set to Synchronous Commit and Readable secondary set to No.

 I thought this was all working fine but when I was doing something unrelated in Microsoft SQL Management Studio I noticed that the Availability Replicas status for the secondary had a red cross by it. I then checked the availability group dashboard and can now see under the secondary:

Synchronization status: Not Synchronizing

Failover Readiness: Data Loss

This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.

At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.

The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database should be in the SYNCHRONIZED state.

I have checked firewall ports and 5022 is open and not blocked. I have also checked netstat to confirm sqlsrvr.exe is using 5022 which it is. I am now starting to think this could be permission related.

Can anyone help point me in the right direction on where to go from here?

Many thanks!

解决方案


这篇关于此辅助副本未连接到主副本。连接状态为DISCONNECTED的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

07-15 04:15