Mirror And Witness Connection In A Disconnected State Immediately After Adding Witness Server To Mirror Session.
Jan 31, 2008
After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
Any idea's why the state between Mirror and Witness Connection remains Disconnected?
I am using SQl Server 2012 Database Mirroring with around 40 gb as mdf and 1 gb as ldf. Now my ldf size increased . How to reduce ldf size while mirror enabled with mirror server and witness server. Can shrink the ldf with mirror enables.
the Mirror Server is not connected to the Witness Server.
Mirror Server and Wtiness Server are instances on one server.
I get this error:
" 2007-06-28 17:08:12.77 spid23s The server instance Witness rejected configure request; read its error log file for more information. The reason 1451, and state 3, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry."
In the SQL Profiler for the Witness Server I get "An error occurred while receiving data" Error 64.
In the witness server logs is nothing depending on this.
The connection between the witness and principal and the mirror and principal are all right. I have created User logins with certificates on the same way on all instances.
missing witness server information and the fail-over is broken suddenly? 4:00am no maintenance job. I have one sql job on 10pm for backup on database transaction log only.
I can see the primary have problem then perform fail-over to mirror database, the auto fail-over was broken.
I re-build the sql mirror is OK , but i want to find the root cause.
Windows application event was full when there have many failed event, i have increase log size for application event. Â
I can establish the mirror with the principal and mirror but cannot add the witness (error 1456) all machines are SQL Server 2005 standard edition service pack 2 principal and mirror are windows server 2003 and witness is windows xp
Hi guys , I would like to know what's the exactly results able to get in this following scenario.
Server A : Principal
Server M : Mirror
Server W : Witness
1) Firstly, disable server M, following by server W. So probably i will unable to connect to Server A eventhough it acts as a principal.
2) Next, if I enable either server M or server W , what will I able to get actually ? Is it the mirroring works like the article which written in Microsoft page ?(http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx#ETPAE)
At here, I get an error message and unable to continue the mirroring section. ( "Database EMS is enabled for Database Mirroring, but neither the partner nor witness server instances are available: the database cannot be opened." or "Database 'EMS' is being recovered. Waiting until recovery is finished." )
3) If I enable both server M and server W, the mirroring continue to work again.
Can I have any assistance on (2) issue? Thx for the assistance.
I have SQL 2005 mmirroring sucessfully working in an ASP.NET 2.0 web application. I also have session state being maintained in SQL Server using the built-in functionality in ASP.NET. The problem is, even with "allowCustomSqlDatabase=True" and specifying a failover partner in the DSN, it appears that ASP.NET does not work with the failover partner. It always tries to get the session info from the "data source" server specified in the DSN.
Is there a way to get the session state to fail over to the mirrored server without writing a custom session state provider?
I'm having a problem with two mirrored databases, using SQL Server 2005 SP2, that autmatically failed over last night for unknown reasons. I was trying to fail them back over to the primary SQL server because it says the mirror is disconnected and out of sync. Other databases failed over too, but I was able to fail those back over without a problem. It's just these two. I removed the mirror from the secondary server thinking that this would allow me to restore the database back on the primary server, but that didn't help.
These two databases show a status of (Principal, Disconnected / In Recovery) and I still cannot do anything with the two databases on the primary server. When I try to pull up the properties for them, I get the following error:
"Database <Name> is enabled for Database Mirroring, but neither the partner nor the witness server instances are available: the database cannot be opened.(Microsoft SQL Server, Error: 955)"
I cannot delete, detach, Alter or do anything with the databases. If I could just delete them that would be fine so I can just do a restore, but I can't seem to do anything.
Does anyone know what I can do to resolve this problem.
While a database upgrade schema changes were being made the Mirror became disconnected will this recover itself when it reconnects or will it be the case that we will have to copy the db files to the Mirror and set it up from scratch.
Hi guys, right now I am having insufficient hard disc space at the secondary server (Mirror side) due to the large db that I have. Therefore, I get a new HDD on the server (Assuming located at drive G) and would like to shift the current mirroring db to that new drive. Is it possible for me to do that ? Hope able to get any suggestion from here ASAP. Thanks.
we config our SAP system to use SQL Server 2005 database mirror. but the mirror server hang by accident, after restart mirror server,the server return to normal,but the mirror can't be resume.
ALTER DATABASE R3P SET PARTNER resume
the error is: Msg 1447, Level 16, State 21, Line 1 ALTER DATABASE "R3P" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command.
I wonder how do I shrink log file in a specific database which in Mirror/Synchronized/Restoring state..So that database is in Mirror server ( High availability ).
I was trying to test mirroring and now would like to delete the mirror database but it says I need to remove database mirroring first. I deleted the endpoint and cannot figure out how to remove the mirroring. Can someone please help.
The 2.0 version of ASPSTATE is slightly different than the 1.1 version in that one table has one additional column and another table uses a different data type and size for the key. The 2.0 version also has a couple additional stored procedures.
We'd like to manage just one session state database if possible so we're trying to figure out if Microsoft supports using the new schema for 1.1 session state access (it seems to work, but our testing has been very light).
Is there any official support line on this? If not, can anyone comment on whether or not you'd expect it to work and why?
We have mirroring setup for 5 dbs, 4 of which are synchronized and 1 which is in "synchronizing" state on the principal and "restoring" state on the mirror. Mirroring for all dbs has been working fine for the past several months and we have a witness that has allowed automatic failover in the past without problems.
This database has several bulk inserts performed throughout the day and am sure there is some latency due to the size of these transactions.
Not sure as to why this is happening all of a sudden, but the db in question has been in this state for the past 12 hrs. I checked the mirroring status on the principal and it states that it is "synchronizing: data is being transferred from principal to mirror", but the mirror server states that db is in "restoring" state. Can anyone suggest as to how I can get the database on the mirroring server to get back to "mirror, synchronizing/restoring..." state? Or suggest on how I can troubleshoot this?
The problem: One server sees the witness, one does not. If the dbs are active on the one that doesn't see the witness and I shut that server down everything works as it should. However, if the dbs are active on the server that sees the witness and I shut that one down the mirror does not take over because it can't see the witness and form a quorum. It throws Event ID 1438 every 20 seconds complaing "The server instance Witness rejected configure request...The reason 1451, and state3, can be used for diagnotics by Microsoft...."
The scenario: I finished setting up a mirror in a WORKGROUP, by going through the GUI and then at the choosing not to start the mirror. That allowed me to modify the NETBIOS names and change them to IP addresses in order to get around the FQDN requirement that I can't fulfill since the servers are in a workgroup. They are in the same subnet and can run SQL queries against each other.
When I query sys.database_mirroring from the database servers I get this on the good server: mirroring_witness_name mirroring_witness_state_desc ---------------------------------------------------------- TCP://155.17.92.63:5022 CONNECTED TCP://155.17.92.63:5022 CONNECTED
And this on the bad server: mirroring_witness_name mirroring_witness_state_desc ----------------------------------------------------- TCP://155.17.92.63:5022 DISCONNECTED TCP://155.17.92.63:5022 DISCONNECTED
here's are the results from sys.database_mirroring_witnesses database_name principal_server_name mirror_server_name safety_level safety_level_desc -------------- -------------------------- ------------------------- ------------ ------------------ dbadmin TCP://pscdaltpscom20:5022 TCP://155.17.92.65:5022 2 FULL dbtest TCP://pscdaltpscom20:5022 TCP://155.17.92.65:5022 2 FULL
Oddly, the server that I created the mirror from registered itself with it's NETBIOS name even though I told it to use an IP address. However, that's the one that is working properly. I think this might be a red herring.
Does anyone have any ideas why my second server can't communicate with the mirror? Any clarifications I can make? I have been completely unable to find a step-by-step guide to creating mirror databases outside of a domain...so if someone knows of one please point me that direction.
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'xxxxxx'. (Replication.Utilities)
I am unable to add witness server to my mirror configuration. my error log is throwing error'Connection handshake failed. The certificate used by the peer is invalid due to the following reason: Certificate not found. State 89'.
I am getting this error while trying to setup mirroring. "Neither the partner nor the witness server instance for database "shop" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)"
I am just using principal and mirror server, there is no witness server. I have tried fully qualified name and ip for the servers also. I can connect from the principal server to the mirror server using the management studio and it also creates endpoints on prinicipal and witness. But then gives me an error that it cannot find the instance of the mirror server and if I try again it gives the error above. I can also telnet to port 5022.
I have used -T1400 as the startup parameter.
I did the backup and recovery based on this link http://msdn2.microsoft.com/en-us/library/ms189053.aspx and the mirror server is in recovery mode now.
I have two 64bit SQL Server Std servers that will be principal and mirror. I also need to stand up a witness. I already understand that the witness can be any version of SQL Server, but can the witness server be 32bit given the principal and mirror are 64bit?
We've been running a mirrored database (using certificates since we don't have a domain) and it's all working well. Last week we decided to add a witness for automatic failovers, but for some reason I just can not get the witness to connect to the Partner2 server.
See screenshot here
Please help me troubleshoot this - I re-created the endpoints / users / certificates but it's still not working. Where can I get more information on what exactly the problem is? Can I test the endpoints somehow?
Hi guys, right now I am facing this scenario several times and I wonder why it can be happen. Both SQL servers are in Enterprise SP1 edition. The mirroring setup can be work fine to me. Once my principal get attacking by DDOS, then mirroring session change the status to 'DISCONNECTED'. However, after DDOS attack solved and line connection gets back on the principal server, the mirroring session still remain to the status ('DISCONNECTED'). If I restart the SQL services on principal server or mirror server, then only the mirroring session change to 'SYNCHRONIZING' status. Does anyone faced this happen before? I need some assistance on it and hope able to get any explanation or solution from you guys. Thanx and have a nice day.
Sorry I didn't know the best forum for this question.
I have 3 SQL 2005 x64 servers on my remote domain. 10.1.10.65 is the primary 10.1.10.66 is the mirror 10.1.10.67 is the whitness.
All 3 machines run the MSSQLSERVER service as a domain admin user acount, and all of the other servies use LocalSystem. All machines are configured to use the default instance name of MSSQLSERVER.
I have another seperate server ON THAT DOMAIN which runs IIS and ASP Classic. I installed the SQL Native client on that machine.
Here is the ASP code: ----------- <% dim strConnString, objConn, rs, sql
sql = "SELECT * FROM DFW" Set objConn = CreateObject("ADODB.Connection") objConn.ConnectionString = strConnString objConn.CommandTimeout = 300 objConn.Open
SET rs = Server.CreateObject("ADODB.Recordset") rs.CursorLocation = 3 rs.Open sql, objConn
Do While Not rs.EOF Response.Write rs(0) & " " rs.MoveNext Loop
rs.close objConn.close set objConn = nothing set rs = nothing %> --------------------------------
If I run this code on the server on the SAME domain and shutdown MSSQL services on the primary machine the Failover server starts working an serving data requests.
It I then take that code and run it from another REOMTE domain, I can connect to the primary server and get data, but when I force a failover for testing it refuses to connect the the MIRROR server.
In the error log on the primary server I see 12 errors. There are 4 sets of the following 3 errors, as SQL will try to connect 4 times before failing.
1) Date 4/7/2008 12:00:39 PM Log SQL Server (Current - 4/7/2008 12:00:00 PM) Source Logon Message Login succeeded for user 'sa'. Connection: non-trusted. [CLIENT: 10.1.3.79]
We have 2 data centers, site 1 and site 2. Â Site 1 is generally our primary, and site 2 is our Disaster Recovery (DR) site. Â I want to setup a SQL instance to have extremely high availability. Â Therefore I was looking at using DB mirroring, with synchronous data writing, high-safety and auto-failover. Â This requires the usage of a witness server.My problem with this setup, is that if the witness and principal are both at site 1, if site 1 goes away (power failure, asteroid impact, lol, anything else that would be a *true* DR scenario), then there is no failover to the mirror server at site 2. Â However, if you put the witness at site 2, anytime the WAN link between site 1 and site 2 has an issue, the DB will auto-failover to site 2. Â Is the reason for the recommendation of the witness being at the primary site because the thinking is that WAN link failure is likely more common than a *true* DR scenario that takes out all of site 1?
Does anyone know where I can get SQL Server 2005 witness hosting? Our primary server is in Vermont and our DR site is in New Hampshire. I would like to set up a witness server somewhere off the east coast. I don't want to have to purchase a new server and pay big prices for colo.
Is there such a thing as witness hosting? Would someone be willing to host my witness and I can host yours?
We are trying to set up database mirroring. The mirroring works for the principal and mirrored databases (set up via Management Studio), but when we try to set up the witness database, we are getting the error message €œThe ALTER DATABASE command could not be sent to the remote server instance 'TCP://€¦ (Error: 1456)€?. The same occurs if I try to do €œALTER DATABASE xxx SET WITNESS =€? in TSQL. We are using the Standard edition for all three. We have tried using several different servers for the witness. All same user, same domain. Any suggestions? Thanks.
I have set up a SQL Express sytem to act as a witness....all are under the same admin account, all can ping and see each other. When I attempt to start a mirror session, it fails to issue an "ALTER Database" comment and the mirror setup is set to "High Performance".
This is my first time setting this up and it took over a day to do this as it is a relatively new concept, I am not DBA, just a S/W developer set up with the task of communicating with two DB instances which are mirrored. A couple of questions:
1) Is it normal to see the mirror instance in the following mode: (Mirror, Synchronized/Restoring)?
2) Any special steps required on SQL express besides enabling TCP/IP within the Configuration manager? It doesn't need the same instance of the same databaes on it, does it?
I have managed to set up mirroring on SQl 2005 however i have a come across a problem that i dont know how to resolve.
Im running the mirroring with 'High Safety with automatic failover.'
If i instagate a failover on the Principal Database, the mirror becomes the Principal, and vice versa ... great .. how ever .. i tried the golden test by making the principal server dissapear by yanking out the network connection, expecting the mirror to become the principal.....nope it just stays there in a disconnected / restoring state which isnt any good to man nor beast . I thought that the Witness should have dectected that the principal database had 'dissapeared' and would have made the mirror the Principal.
Any pointers on where i might have gone wrong in the setting up process, i used the mirror wizard
I removed mirroring on a configuration that is currrently working. Next, I moved the witness server to another IP and changed the FQDN (I patched the machine to another newtork, added a FQDN to our DNS server and reconfigured the machines IP information. I can ping the witness at its new address from the principal and the mirror).
Would changing the Witness's IP and FQDN prevent Database Mirroring from being setup after the certificate has been created and distributed to the principal and mirror instances under the old IP and FQDN? Should the endpoint be reconfigured and a new certificate be generated and distributed after an IP and FQDN change?
