Fortunately this problem is in our test network, but I do need to get this working again. These servers have been shut down and restarted several times since the last time I worked in this test environment.
In this environment, I have a 3-node Exchange 2010 DAG (EX2010DAG) and a 2-node Exchange 2013 DAG (EX2013DAG). The 2 nodes in the 2013 DAG are EX2013A and EX2013B. The 2013 databases are all dismounted, and they are all listed as being active on EX2013B. There is only one mailbox remaining on Exchange 2010; the rest have been migrated to 2013.
The 2010 DAG seems to be working properly, but none of the databases in the 2013 DAG will mount. When I try to use the Mount-Database cmdlet against any of them, I get the message: "Failed to mount database "<databasename>". Error: An Active Manager operation encountered an error. To perform this operation, the server must be a member of a database availability group, and the database availability group must have quorum. Error: Unable to read from the cluster database. This may occur if the server has recently been removed from the database availability group. [Server: EX2013A.lab.mycorp]." (The designation .lab.mycorp is an internal domain and approximates our production environment.) I noticed that regardless of which database I try to mount, the server listed in the error is always EX2013A.
When I open Failover Cluster Manager, there is no cluster listed. I clicked on "Connect to Cluster"then clicked "Browse", and the DAG names (one 2010 and the other 2013) are both listed. When I select the 2013 DAG name and try to connect, I get the error "Cluster EX2013DAG not found".
We test more that just Exchange in this environment, so rebuilding the entire Domain from scratch would create a lot of work. While I would prefer to mount these databases intact, I would also be OK with getting Exchange 2013 back up and running with empty mailboxes for all the existing users if that is all that is available to me.
What do I need to do to correct this?
Thank you for your help.