?
Solved

Exchange 2010 DAG FSW Not Setup Correctly

Posted on 2011-10-01
6
Medium Priority
?
754 Views
Last Modified: 2012-05-12
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
Comment
Question by:vegas588
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 

Author Comment

by:vegas588
ID: 36897337
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
 
LVL 24

Expert Comment

by:Rajith Enchiparambil
ID: 36897603
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
 

Author Comment

by:vegas588
ID: 36907295
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
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 24

Expert Comment

by:Rajith Enchiparambil
ID: 36911909
Delete all FSW shares that you are not using and restart the server
0
 

Accepted Solution

by:
vegas588 earned 0 total points
ID: 36921330
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
 

Author Closing Comment

by:vegas588
ID: 36941300
partially answered by all participants
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses
Course of the Month8 days, 10 hours left to enroll

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question