• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 761
  • Last Modified:

Exchange 2010 DAG FSW Not Setup Correctly

I've given up on TechNet forums as no one there can ever answer a question...back to EE!

We have a customer with an odd problem in the setup of their Exchange 2010 SP1 DAG. They have 2 AD Sites and each site is physically different. One HQ and one dedicated DR site. Each site has a combined CAS/HUB server and a Mailbox server for a total of 4 servers (all virtual). The DAG is therefore a 2 member DAG, with each node in a separate physical site. It is in DAC mode. Although the File Share Witnesses are listed correctly in the DAG properties, when you look at the Failover Cluster Manager, there are 3 FSWs listed. Someone clearly added a 3rd one in an attempt to "fix" something and the FSW in the primary Site that is listed is an old one no longer used. Hence, in the Summary at the top of the Failover Cluster Manager, there is a warning that the FSW is down. The net effect of all this is that the Failover Cluster manager does not "see" the real FSW in the primary site (it actually lists the original one and marks it as "Offline") and therefore the 2nd Mailbox server is the 2nd vote in the DAG. So, when the 2nd Mailbox server is rebooted, the databases dismount in the primary Site.

How can I clean this up? I assume there are some Cluster commands that can add/delete the FSWs listed and essentially re-do them? What effect will that have on the DAG? Need answers quickly. Thanks.
0
vegas588
Asked:
vegas588
  • 4
  • 2
1 Solution
 
vegas588Author Commented:
I was able to find out how to add the FSW manually using the More Actions menu in the Failover Cluster Manager. However, I find this messy because it seems that I can only add FSWs and not delete the existing ones. I also noticed that during the failback to the primary datacenter, the cluster core resources did not move to the primary HQ. I had to manually use cluster commands from here to force them back: http://blogs.technet.com/b/timmcmic/archive/2010/05/25/exchange-2010-cluster-core-resources-the-replication-service-and-active-manager.aspx

0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
You shouldn't be managing things from failover manager, but from Exchange. Try pointing Exchange DAG to a new FSW. Restart Exchange and cluster services & see whether it corrects it.
0
 
vegas588Author Commented:
Made some progress, but I am not seeing what I expect. The primary FSW is listed in the Failover Cluster Manager, but at the top, in the Summary section, it is still pointed to an old FSW. It's as though Exchange 2010 is not updating the Failover Cluster Manager or should it?
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Delete all FSW shares that you are not using and restart the server
0
 
vegas588Author Commented:
Was able to figure out some of this through this blog http://www.shudnow.net/2011/08/05/exchange-2010-site-resilient-dags-and-majority-node-set-clustering-part-1/

FSW cannot be easily deleted because it is considered a Core Cluster resource.
0
 
vegas588Author Commented:
partially answered by all participants
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now