Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a MS SQL 2008 R2 Fail-Over Clustered Instance running between two Windows 2008 R2 servers using the inbuilt Windows Clustering features, that is working with a DTC and Quorum with a disk based Witness. This has been working fine for months and little concerns with the functionality.

I've now been asked to add DB Mirroring to an alternate site (asynchronously) but when setting up the Mirroring partners the Endpoint on the cluster fails to respond. Pinging the Cluster Name returns the clusters IP so I'm not sure how to confirm its routing to the active host.

Firewall port has been opened on both the remote server and the two clustered servers.

Can anyone direct me on the steps you need to take to do Asynchronous database mirroring on a W2008R2/MSSQL2008R2 Fail-Over Cluster in order to make the Endpoint on the cluster reachable by the mirror?

share|improve this question
up vote 0 down vote accepted

Apologies for the wasted time, I didn't realise at the time but when I restored the database to the second server I didn't select restore with NO RECOVERY. After making the change and attempting to mirror again the process worked.

I still don't understand why I was receiving an error indicating the cluster was not responding considering the problem was on the stand-alone mirrored server.

share|improve this answer
What was the error message you received on the mirror server when trying to connect? These would likely be in the SQL Server error logs on the mirror server. – shiitake Mar 7 '13 at 16:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.