>I am having problems with a SQL 2005 Mirroring setup.
>
> Here is the configuration:
>
> 4000A - IIS NLB/SQL 2005 Witness
> 4000B - IIS NLB/SQL 2005 Backup
> 4000C - SLQ 2005 Primary
>
> All three servers have 3 nics - 1 internet facing (and for A & B
> configured for NLB), 1 for backend communication and 1 in network with
> a backup SAN. The backup LAN does not allow communication between the
> servers.
>
> The public facing IPs are on the 192.168.68.0/24 range.
> The internal facing IPs are on the 192.168.68.0/24 range.
>
> While all servers are up, everything is fine. I have configured the
> SQL mirroring for the four databases required and it works fine. The
> databases show up as being mirrored, in SQL Management Studio, I can
> fail them over manually using the failover button and they all
> continue to respond.
>
> My problem occurs when they failover due to a failure on the main
> database server - 4000C.
>
> In this scenario, it appears that the backup server (4000B) loses
> connectivity to the witness server (4000A) for some reason.
>
> The servers realise 4000C has gone down, automatically fail over to
> 4000B, but then stop taking requests for the database on 4000B. In
> Management Studio, the databases show up as (Principal, Diconnected /
> In Recovery).
>
> If I try to get their properties, it tells me:
>
> "Database Preview is enabled for Database Mirroring, but neither the
> partner nor witness server instances are available: the database
> cannot be opened. (Microsoft SQL Server, Error:955)"
>
> While this is happening, I can telnet to the witness server from the
> backup server by name or IP on port 5022, so it doesn't appear to be a
> network connectivity problem. Pinging by name shows that it is
> resolving to the inside (.69) IP address, so it getting confused with
> the NICS doesn't appear to be the problem either.
>
> If I failover manually to 4000B and then shutdown 4000C, I get the
> same problem.
>
> I dumped the logfiles from c:\program files\Microsoft SQL Server\MSSQL.
> 1\MSSQL\log for all three servers across a shutdown of 4000c while it
> was primary, and then a startup of 4000c - it can be viewed at
>
http://www.arrowtech.com.au/logfiles.txt
>
> As far as I can see this is a pretty tough one - Google isn't giving
> me a lot to go on and I am not exactly an SQL guru - I would
> appreciate anyone's suggestions here.
>
> Clayton
>
