Announcement

Collapse
No announcement yet.

MS Exchange 2016 restart/halt issue after DAG configurations

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • MS Exchange 2016 restart/halt issue after DAG configurations

    Hi,

    Previously I had only one exchange server, it was running smoothly but I planned to create DAG for high availability. my environment became:

    DAG: dagname

    Node1: mail1 (2 networks, one for MAPI and one for REPL)

    Node2: mail2 (2 networks, one for MAPI and one for REPL)

    both nodes are CAS+MBX. DAg is ok, failover is OK. cluster configurations and validation is OK except some windows updates on both servers. my exchange server version is same on all servers.

    after creating DAG, one of my mail servers goes down after some days (2-3) days. either it becomes halt or restart automatically. if it restarts and comes back, everything is OK but if it halts then I have to manually power off and then ON.

    event id 1135 occurs in failover cluster when one of mail servers halts.

    Why my server either mail1 or mail2 restarting or halt after creating DAG?

    one more thing, when mail1 downs, OWA and Activesync are not working from external network. I guess rpcClientAccessServer is set to mail1 on all databases. how to change rpcClientAccessServer? EMS command

    set-mailboxdatabase dbname01 -rpcClientAccessServer mail2

    is not working. please suggest.
Working...
X