July 7, 2013 at 6:22 pm
We are running SQL Server 2008R2 RTM (10.50.1617)
We get time out messages that read like "the mirroring connection for database has timed out after 90 seconds" too often. Now I have only been a DBA for 6 months of my life, but these messages pop up at least once a week, and if we had not increased the threshold fail overs would be happening regularly as well.
I would like to know if a more seasoned DBA's opinion on this. I talked with the systems/networking guys and they see nothing unusual in terms of the computers performance and network traffic and have looked at the ip traffic logs on the switches.
I am trying to push them to update to service pack 3 hoping that will smooth things out. I also read that upping the cpu priority could help. I would love to hear your opinions, and if i should pressure them to do this. Thanks
July 7, 2013 at 7:11 pm
I have noticed this sometimes when full backups occur at night. May be due to network bandwidth issue. But this has not posed a problem to me so far.
M&M
July 7, 2013 at 9:03 pm
A separate network for backups is something my previous company took advantage of, the current one may not. I have to check.
July 8, 2013 at 1:38 pm
Most probably mirroring timeouts occurs due to the network issues...
How ever you can check the mirror server disk size since there is a
Possibility timeouts can trigger due to the disk queue length...
By increasing disc size this will fix..Hope this helps...
Thanks,
Vasan
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply