I was reviewing our Application logs on our 3 Exchange 2016 servers and came across the following error message.
The log copier was unable to communicate with server 'Exchange1.Domain.com'. The copy of database 'MailDB03\Exchange1' is in a disconnected state. The communication error was: An error occurred while communicating with server 'Exchange1'. Error: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.
Our current setup is 3 exchange 2016 servers CU16. Exchange1 and Exchange2 are in our primary datacenter site. Exchange3 is in our backup datacenter site. All databases are active on Exchange1. I don't see the errors in the application logs on either of the other 2 nodes in our primary datacenter, only on Exchange3.
When I run the following commands I get:
Get-MailboxDatabaseCopyStatus * All 5 databases across the three nodes are healthy. CopyQueueLength and ReplayQueueLengths are 0. Occasionally they show 1 on ReplayQueueLength on either of the two passive nodes (Exchange2 and Exchange3).
Get-MailboxDatabaseCopyStatus -ConnectionStatus | FT Identity,IncomingLogCopyingNetwork on Exchange2 shows
MailDB01\Exchange2 {Exchange1,MapiDagNetwork} for all five databases
On Exchange3 (DR)
MailDB01\Exchange3 {Exchange1\MapiDagNetwork, An error occurred while communicating with server 'Exchange1'. Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.}
I get the above message on all 5 databases on exchange3.
Test-replicationhealth on all nodes passes all tests.
I am thinking that maybe something with the fact that Exchange1 and Exchange2 are on the same network and Exchange3 is on a separate network in the Backup datacenter? Everything can ping each other.
I am going to do some failover testing tonight to see if there is any impact but if anyone has any ideas what this is or how to correct it please let me know.
Thanks