Exchange 2013 DAG

Hey guys

Ok, here is what I have.  Client setup DAG and it has worked flawlessly for quite some time.  Unfortunately they weren't paying attention to the File Share Witness server and it crashed (the DAG didn't give any warnings, it just kept working).  It was setup on a Hyper-V machine and the physical machine actually crashed and since they didn't realize that the File Share Witness was on it, they simply wiped the machine and set it back up without the File Share Witness.  Now, I am tasked with fixing this.

Here are my thoughts. They have two servers on site and one offsite.  All three are replicating to each other successfully.  My idea was to make one server the primary one with all the mailboxes active on it.  They remove the other two servers from the group, one at a time, and then remove the DAG service.  Restart the primary server and create the FSW back on the old Hyper-V.  Setup all the permissions as before and then add the DAG service to the Primary Exchange server and then add the other two servers back.

Sounds good to anyone?  Is that all the right steps as far as you can tell?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:

So basically you're trying to perform a server Switchover. In that case move all the active Mailbox DB to one or more servers. Then remove the DAG service one at a time. However if the issue is related to the FSW then you can set it using the command don't need to remove the servers from the DAG Service. Refer the below links for understanding Server Switchover & DataCenter Failover

Set-DatabaseAvailabilityGroup <DAGName> -WitnessServer <ServerName>

jonmenefeeAuthor Commented:
Thank you. I will check out those links. Yes. The FSW is dead and gone so I need a new one
Simon Butler (Sembee)ConsultantCommented:
If the FSW is dead, just create a new one. No need to do anything with the DAG.
All that means is you need to add Exchange Trusted Subsystem to the local admin of the server you are going to use as the FSW, then change the values on the properties of the DAG. Give it a few minutes to replicate and all should be well.

The DAG kept running because the FSW is only used when a failover event occurs and it is required to make the decision on which server to keep alive.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jonmenefeeAuthor Commented:
That is the best news I have heard all day.  Thank you Simon!!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.