September 27, 2006 at 2:21 pm
We are testing mirroring in or datacenter and are so far pleased with it. When we manually failover ( a "soft failure" ) the applications switch with little interuption.
If we cause a "hard failure" by either stopping SQL Server or unplugging the network cable on the pricipal server, Mirror Monitoring indicates the Mirror has become the Principal and the original Principal is disconnected. Which is correct.
The problem is the new principal does not accept incoming transactions.
The only way we have been able to bring the mirror back is to restatr SQL Server and SQL Agent on both partners in the mirror.
Our applications are all running .Net Framework 2.0.
Greg Roberts
September 28, 2006 at 10:43 am
Are you using syncronous transactions?
September 28, 2006 at 11:22 am
Yes.
We configured for high safety with a witness.
Greg Roberts
September 29, 2006 at 3:47 am
What happens when you try to connect using Management Studio and run queries after failover?
Do you get any errors?
Also try a creating a UDL from a client machine.
Also check the configuration for the client connections. They need to be setup to try to secondary server if the initial connection (to the original principal) fails.
October 2, 2006 at 12:18 pm
No errors are received, the database is just unresponsive. On both the principal and mirror. It's like it never finishes failing over.
Greg Roberts
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply