Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)

公司一SQL Server镜像发生了故障转移(主备切换),检查SQL Server镜像发生主备切换的原因,在错误日志中发现下面错误:

Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)

Date        2019/8/31 14:09:17

 

Log     SQL Server (Archive #4 - 2019/9/1 0:00:00)

 

 

 

Source      spid35s

 

 

 

Message

 

Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://xxxxx:7022'.

检查见证服务器的系统日志,发现如下错误信息,提示见证服务器超过10秒仍然无法得到数据库的响应,请检查服务或网络问题( Check the service and network connections.)

Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)

分析到这里,我只能猜测SQL Server服务异常或网络异常问题导致见证服务器超过10秒无法访问主体服务器,从而引起了主备切换,找系统管理员协助帮忙分析时,系统管理员确认周六14点那个时间段正在使用Veeam Backup & Replication备份镜像的主体服务器(他正在测试使用Veeam Backup & Replication备份VmWare虚拟机),但是这个Veeam Backup & Replication备份是否会引起网络中断呢?于是,周一我们找了个时间点,测试Veeam Backup & Replication 备份是否真的会导致网络中断,测试过程中发现还真的引起了网络中断(暂时还不清楚是设置问题,还是其他机制方面原因引起的),测试过程确实验证了Veeam Backup & Replication 备份导致网络中断,引起了镜像的主从切换,特此记录一下这个案例!

上一篇:I.MX6 linux tslib Corrupt calibration data


下一篇:svn hooks的使用demo