question

InnocentHeartvoice-2401 avatar image
0 Votes"
InnocentHeartvoice-2401 asked InnocentHeartvoice-2401 commented

Exchange 2019 DAG File Share Witness folder is not creating

I have configured Exchange 2019 DAG of three Exchange 2019 servers, the DAG is working fine as databases are switching to other server if primary server goes down but I notice that FSW folder is not created on the File server. I changed the Witness server and created new directory on other server through Power-Shell and cmdlet ran successfully without any error but no directory found on new server in Witness folder. Assigned all the required permission and added Exchange Trusted subsystem with full control.

Kindly assist.

office-exchange-server-administrationoffice-exchange-server-connectivityoffice-exchange-server-itpro
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.

AndyDavid avatar image
0 Votes"
AndyDavid answered

In a odd number DAG, the File Share Witness is not used.
Its only used when there is an even number of members in the DAG

https://docs.microsoft.com/en-us/exchange/high-availability/manage-ha/manage-dags?view=exchserver-2019#dag-witness-server-and-witness-directory

193750-image.png



image.png (77.0 KiB)
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.

InnocentHeartvoice-2401 avatar image
0 Votes"
InnocentHeartvoice-2401 answered InnocentHeartvoice-2401 edited

Hello Andy,

Thanks for your valuable response. I was more curious the reason is when I executed the cluster validation test having this warning message. The cluster is not configured with a quorum witness. As a best practice, configure a quorum witness to help achieve the highest availability of the cluster.

The other disturbing message was on the Server Manager: Under Manageability - Online- Data retrieval failures occurred on the DAG servers name and IP addresses.

I was thinking the main reason of FSW folder is not creating because of these errors.

Can you please provide your usual support on these error and warning.

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.

AndyDavid avatar image
0 Votes"
AndyDavid 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.

InnocentHeartvoice-2401 avatar image
0 Votes"
InnocentHeartvoice-2401 answered InnocentHeartvoice-2401 edited

There is no error message while creating DAG even as I mentioned that FSW directory on other server was successfully created. One more thing the cluster quorum type = Majority

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.

AndyDavid avatar image
0 Votes"
AndyDavid answered

thats expected since you have an odd number of node
cluster quorum type = Majority

If you had an even number of nodes in the DAG, it would be "Node & File Share Majority"

You dont need the FSW with odd members

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.

InnocentHeartvoice-2401 avatar image
0 Votes"
InnocentHeartvoice-2401 answered InnocentHeartvoice-2401 commented

What about the second part of my question:

Server Manager: Under Manageability - Online- Data retrieval failures occurred on the DAG servers name and IP addresses having message. Kindly assist.

· 4
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.

Hi @InnocentHeartvoice-2401,

Below is a related thread discussed the same issue:
Win Svr 2016 VM error in Server Manager: "Online - data retrieval failures...
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

open command prompt with admin rights and execute it as below:

 cd C:\Windows\System32\wbem\AutoRecover 
 for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 Votes 0 ·

I had executed the cmd but nothing happened, the error message is still showing.

0 Votes 0 ·
joyceshen-MSFT avatar image joyceshen-MSFT InnocentHeartvoice-2401 ·

Hi,

You could also check if your issue is related to the registry key mentioned here: Server Manager: Under Manageability - Online- Data retrieval failures occurred


0 Votes 0 ·
Show more comments