Hi all,

We have 2 Exchange 2019 servers in a DAG (Primary and DR sites).  Server 2022.

We have one witness server which is in the same datacentre as the Exchange server at the primary site.

Whenever the witness server is rebooted, failover clustering changes the DAG DNS object to point to the DR site.  Both nodes stay up.

First of all, can someone advise why this is the case?  Both Exchange servers have communication at all times and the cluster is healthy.

Secondly, is there a way to failback the cluster without pausing the DR node?  I usually Pause and Drain Roles on the DR Exchange node, then Resume without failing the roles back.

thanks

jc

​Hi all, We have 2 Exchange 2019 servers in a DAG (Primary and DR sites).  Server 2022. We have one witness server which is in the same datacentre as the Exchange server at the primary site. Whenever the witness server is rebooted, failover clustering changes the DAG DNS object to point to the DR site.  Both nodes stay up. First of all, can someone advise why this is the case?  Both Exchange servers have communication at all times and the cluster is healthy. Secondly, is there a way to failback the cluster without pausing the DR node?  I usually Pause and Drain Roles on the DR Exchange node, then Resume without failing the roles back. thanks jc  Read More

​