2 Node DAG Not Working as Expected

A client has a 2 node DAG, with each node in a different AD site and different physical site. Active/Passive sites. Each site also has 1 combined CAS/HUB server. The DAG is in DAC mode (DagOnly). There is some odd behavior in the cluster and we spent a good deal of time trying to figure out the issue. Am I correct in thinking that we should not be able to just move the active database copy to the DR site? We should have to go through the entire Datacenter failover scenario using the cmdlets as defined here: http://technet.microsoft.com/en-us/library/dd351049.aspx

Also, in the cluster resources, I see the primary FSW and the Alternate FSW. Yet, in my lab that I setup to mimick their environment, I only see the primary FSW. Should the alternate FSW be listed in a normal setup?

Who is Participating?
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.

A file Share Witness is required for a cluster with an even number of nodes, in the event of a failure of the primary node, the cluster will be left with an odd number and thus an FSW is not required to ensure quorum. In your DAG, the FSW should be in the primary site, with the normally active DAG node.

When DAC mode is enabled, the databases are not supposed to automatically activate in the event of a failure however your are not limited when manually activating a database copy hosted on the other node.  If you are manually activating a copy then this should come live and this is expected behaviour.
vegas588Author Commented:
I'm not sure I understand completely. In their setup, we have no need to use the commands from that article becuase I can activate the databases whenever I want to. This would mean there is no point to all of those commands:

Are you saying that these commands will play no role for them, because that is what i am seeing? If we reboot the primary CAS server or if we reboot the primary DAG Mailbox server, the databaes automatically failover.
vegas588Author Commented:
I was able to clarify the expected behavior from Elan Shudnow's excellent posting on how the quorum works: http://www.shudnow.net/2011/08/05/exchange-2010-site-resilient-dags-and-majority-node-set-clustering-part-1/. Therefore, we can expect to mount databases in the DR site without initiating a complete failover assuming we have only one voter down. However, we know that if we reboot the CAS server in the primary datacenter (which is the Primary FSW), the Databases failover automatically to the DR site. That should not be. We also noticed that in the Failover Cluster Manager, the Alternate FSW is also listed as a Cluster core resource. I have looked at other DAGs and I have not seen this. Any other thoughts on why this automatic failover would occur?

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
vegas588Author Commented:
partially answered.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.