Bobcares

The mirroring connection to has timed out – Quick Fix!

by | Jan 8, 2020

Looking for a solution to the error ‘The mirroring connection to has timed out’? We can help you.

The failover mechanism within database mirroring is designed in such a way that the instances send across a ping within each other to understand if they are alive.

At Bobcares, we often get requests from our customers to fix the connection timed out error as part of our Server Management Services.

Today, we’ll see how our Support Engineers fix this error quickly.

 

What causes mirroring connection to has timed out error to occur?

The error message ‘Mirroring connection to has timed out’ relates to Database Mirroring failover procedure.

With the High Availability mode of synchronous Database mirroring with automatic failover there are three servers that are involved. They are Principal, Mirror, and Witness.

The three servers constantly ping each other. If the Principal instance didn’t receive any responses to “Ping” for 10 seconds from Witness then it shows the below error.

The mirroring connection to has timed out

 

Common reasons of pinging response failed

  • Slow network connection or network reliability
  • Hardware/SAN/VM failure
  • Geographically dispersed mirror partners

So to avoid the accidental database failover we increase the Partner Time Out value.

 

What is Partner timeout?

Partner timeout is the maximum period of time a server instance waits to get a ping message from another SQL Server. The instance in the mirroring session before considering that other instance to be disconnected. We can define the timeout option only on the principal server and specify the timeout period in seconds.

If we set the timeout value between 0 and 4 seconds it automatically set the timeout to 5 second. The default time period is 10 seconds.

 

How we fix the mirroring connection to has timed out error?

The default mirroring time out value is 10 seconds and the error is due to the low partner timeout value. Therefore, we increase the default timeout value.

1. We open the database with SQL Server Management Studio.

2. Then we open a new SQL query windows and execute the following statement.

ALTER DATABASE <dbname> SET PARTNER TIMEOUT 20

We check the Timeout value by the below query.

SELECT Mirroring_Connection_Timeout
FROM sys.database_mirroring
WHERE database_id = db_id(‘<dbname>‘)

 

[Need more help to fix this error?- We’ll help you.]

 

Conclusion

In short, the mirroring connection timeout error occurs due to the partner timeout value. We saw that our Support Engineers fix the error by increasing the partner timeout value.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF