troubleshooting Question

Cluster failover not working (2 Exch with Dag and witness folder) after move of witness folder to new server. It did work before.

Avatar of Laszlo Denes
Laszlo DenesFlag for Canada asked on
7 Comments1 Solution195 ViewsLast Modified:
Hello Everyone and thanks in advance for your expert Exchange 2013 tips, insights and advice.
We have two Exchange 2013 servers (running on 2012R2) with a DAG setup in the past by a vendor.
It had a database availability group witness server and witness directory for cluster failover and it worked.
However, I had to put in a new file server and needed to move the witness directory which I thought I did right, but apparently that is not the case.
Note that the Exchange Trusted Subsystem is a member of the local admin group on the new file server.
Some FYI information to help you help me :-)
The errors indicate (from what I can tell) that the witness folder is not available (permissions or something else), but it is created.
errorsThe share is there for sure and the share permission is everyone full control and the ntfs security permission includes all the right groups, servers, dag etc. as far as I can tell as I replicated the previous setup.sharentfs permThe failover cluster has not changed on the server itself and shows both exchange servers as online nodescluster serverCommand output on the Exchange shows cluster group online, with both Exch member servers part of DAG, shows the witness pointing to right server and share, but the quorumresource file share witness is listing tghfs1 which was the old file server... is that the issue and how do I change that... exzchan commandresultNot good with power shell commands... and if I recall then I did run a command to point it to the new file server tghsvrfile1 and its share... Example: Set-DatabaseAvailabilityGroup -Identity DAG1 -AlternateWitnessDirectory C:\DAGFileShareWitnesses\ -AlternateWitnessServer CAS3 but maybe it did not work or I got it wrong
I also ran some extra commands and the output seems to suggest that the file share witness does indeed point to tghfs1 (even though it is set to point to tghsvrfile1 in the GUI on the exchan admin) wrong1 and wrong2Not sure what is wrong.
Laszlo Denes

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 7 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros