today I will talk about this error :
Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. ---> Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed.. ---> System.ComponentModel.Win32Exception: This operation returned because the timeout period expired
So you will find a looooooot of post about it, but most of time no real answers. You will find good advice like : Check replication network, DNS, order of the NIC in the NIC binding, Services activate on the card, Disable tcp Chimmey, TCPIP Offload…and more and more…cool but at the end I’m pretty sure that you will not be able to add a second Server to your DAG.
No more wait, the root cause is coming from the server. From the NIC configuration of the server. From the Teaming !
OMG ! Yes. I will describe my case.
- 2 Servers on Windows Server 2012 with Hyper-V (A and B)
- 3 Servers Exchange 2010 with CAS, HUB and Mailbox (X, Y and Z)
- the server A has a teaming (windows 2012 teaming) and host the server X
- the server B has NO teaming and host server Y and Z
At this point it is possible
to create the DAG and had Y and Z but NOT X
to create the DAG and had X but NOT Y or Z
the teaming of windows server 2012 is not really compatible with the Failover Cluster service. The teaming is (by default) in “Switch independent” and the algorithm used is “Hash Address”. This algorithm creates a hash based on components of the packet, and then it assigns packets that have that hash value to one of the available network adapters.
So you have to solutions:
– Remove the Teaming on the network card use by the DAG
– try to use the “Hyper-v Port” (it was not working for me)
– try to recreate the Teaming with Intel or Broadcom drivers
If your exchange servers are on a SCVMM with Hyper-V you can group your Exchange DAG Members on one host and setup them to move together in cas of failure of one physical host. If you do a such thing your dag members will be always on the same physical host. It is for me a best practice if you want to continue to use Teaming with DAG.