SQL 2008 Mirroring Issues

views:

516

answers:

SQL 2008 Mirroring Issues

'DNS lookup failed with error: '11001(No such host is known.)'.' for 'TCP://Silver2:15111'.

This pretty much sums up everything. Your networking guys better have an explanation why the DNS name 'Silver2' is lost.

Remus Rusanu 2009-09-10 16:33:40

I am the network guy... and I don't have a good explination why the DNS name is lost *lol*. Initially I thought that was the problem, but while my quorum is broken, I can still ping other stations using the name and also telnet into the endpoint mirroring port.

JohnathanKong 2009-09-10 16:36:35

Well, I'm the guy who wrote the mirroring endpoint code at MS :) If the OS is reporting the DNS lookup error, I gotta take the OS word over yours, no offense. Is the name resolved through DNS or through WINS? Is there anything specific about when it happens (certain time, under load etc). Did you follow any DNS troubleshooting guide to isolate the issue? Ultimately, can you hardcode the name resolution in the `hosts` file?

Remus Rusanu 2009-09-10 16:49:40

Looking at your first answer, the error that you quoted is right, I have lost connection with station 2, the mirror. Sorry, some times I skim through too quickly and miss important details like that. I don't mind that I lose connection to the mirror; that's a different problem altogether. what I am concerned about is that principle and witness are running, so quorum should still be active, and I should still have one active server.

JohnathanKong 2009-09-11 13:13:59

I do understand what SQL is complaining about, but I can't figure out why. The endpoint ports are opened and accepting connections, I can connect through SQL management studio, I can do everything, and everything seems perfect. It's almost like something gets locked on the witness(if that makes any sense). Once I restart the Witness, everything is great. Also, What really confuses me is that I used IP address, so why are the SQL errors using computer names? No where in my Quorum setup do I mention any computer names, so that's really confusing me at this point.

JohnathanKong 2009-09-11 13:17:00

Note that the principal and mirror are reporting to the witness the name of their partner. So if mirror knows the principal by the nickname 'Silver2', then it will ask the witness 'Are you connected to Silver2?'. So you better be consistent and use the same names everywhere, don't mix names and IPs. Also the mirroring protocol is looking up its own machine name at each endpoint and uses it to validate the peer's request. The best option is to use FQDNs as partner and witness name everywhere when you set up mirroring.

Remus Rusanu 2009-09-11 14:53:19

What was happening is that we were having some issues with rebooting stations. Since this is a hospitality industry, the poll displays had a bad driver that was screwing everything up,

JohnathanKong 2010-01-23 02:01:03

ansaurus

tags:

views:

answers:

SQL 2008 Mirroring Issues

related questions