Exchange 2016 DAG unable to seed working database to other servers. After a customer was hacked we had to restore an dold version of the server and import the mail from a copy of the DB on the failover DAG (which also had to be restored, it was the RYUK ransomware team who did a proffesional number on them). now this worked to an extent, the other DAG's are fine and work great but this one will never seed and is shut down with "Error: Communication was terminated by server 'BG-EX-London': Data could not be read because the communication channel was closed". Ive disabled AV etc but it never goes for more than a few seconds.
One clue which I think is the crux here is the database will not mount on its own, I need to manually mount it with the -Force switch before it goes live. Without the Force swithc the error is "Error: An Active Manager operation failed. Error: The database action failed.
Error: Database 'DB1' on server 'Server1' cannot be mounted due to a previous error: At '03/01/2019
09:09:05' the Exchange store database 'DB1' copy on this server appears to be inconsistent with the active
database copy or is corrupted."
So it seems it thinks the other version of the DB is the one that should be live even after Ive removed the DAG copy of it.
Any ideas, this is the only thinhg annoying me after the hack?