question

AndyDelk-7077 avatar image
0 Votes"
AndyDelk-7077 asked Criszhan-msft answered

Secondary Mirror Cannot See Same Witness

Hi all,

We have an issue where the secondary mirror cannot see the witness. The primary has no issues.
So far, we have checked:
1. Using FQDN
2. Ports are open
3. Established Ping
4. SQL servers are all the same version (SQL 2012) - Witness is SQL Express 2012

Any help is greatly appreciated



sql-server-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndyDelk-7077 avatar image
0 Votes"
AndyDelk-7077 answered
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Criszhan-msft avatar image
0 Votes"
Criszhan-msft answered AndyDelk-7077 commented

Hello,

I want to confirm with you what you mean that cannot see witness on the mirror server. What is the current status of the mirror database on both principal and mirror server.

Has the issue been resolved after applying the patch to the SQL Server instance.
Regardless, It is always recommended to install the latest updates for your SQL Server to avoid any problems that have been fixed.

· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Correct, I cannot see the witness on the secondary. I can failover manually without issue.
Currently the SQL server has never been patched, however, why would the Primary still see the witness and the secondary not?

0 Votes 0 ·

There is no problem with two-way manual failover between the two servers.
What do you mean by not seeing it?
The mirror database on the mirror server is not accessible, nor can it be clicked on its properties in SSMS.

0 Votes 0 ·

I can failover manually without issue. The problem is that if the secondary doesnt see the witness server then there wont be an automatic failover.

0 Votes 0 ·
Show more comments
Criszhan-msft avatar image
0 Votes"
Criszhan-msft answered

Hi,

It seems that resetting the witness(removing and re-adding) does not help your problem.

Because you have checked such as FQDN, ports,network, etc. and confirmed that there is no problem, then the problem may still be in the configuration of the database mirroring itself.

In addition if you cannot test another database or reset the entire database mirroring configuration in a production environment, it is recommended to do this and patch the instances during the next maintenance period.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.