Database Activation co-ordination mode uses the protocol DACP.

One of the DAG member will

always have the special memory bit set to 1. If any time any server wants to mount the
Database it is to find the DAG node which has memory bit set to 1 and then it will mount
the Database. If the above split brain syndrome scenario when primary site come up Active
manager will try to find if the DAG is the DAC mode or not. If the DAG is running in DAC
mode then server will have DACP flag set to 0 and try to query all the DAG members for
DACP flag 1. If it finds all the members and member with DACP flag set to 1, then Active
manager running on the DAG member will set DACP to 1 and mount the database. If the
Active manager could not find the DAC member with DACP with 1 then database will remain
unmounted state. This will avoid split brain Syndrome.
Let’s understand DAP with above example :If the network is restored between primary
Datacenter and Secondary Datacenter and primary server is also up then these database
which are is in unmounted state will remain unmounted. This is because during the process
of activation of secondary site exchange servers will evict all the primary DAG servers from
the DAG configuration. So, the members on primary Site contain old information which is no
longer valid and this will not allow primary site Exchange severs to participate in the DAG.

Move-ActiveMailboxDatabase -Server AMBX2 -ActivateOnServer AMBX1

We can check by cluster manager current host server.