Forum Discussion
mailbox databases dismounting frequently without followable reason
I have a 3 node DAG (EX2016, current patchlevel), 2 in "main" AD site and 1 in backup site. It's about 400 users homed in 9 mailbox databases currently. Since a few days on of the nodes in the main...
This is actually funny: I have created a new empty database on the "problem server" and even created passive copies on the other servers, too. This works perfectly, no issues with mounting at all.
Then i removed the copy of one of the existing dbs, cleaned up everything in file system (db and logfiles), too. Restarted infostoreservice on "problem server", ensured the related ad object has been purged, too.
Only then i created a new fresh copy from "main server" (no issues there) to the "problem server" again. This way even the file/folder permissions have been created correctly. However, as soon as seeding of 300 GB was finished), the same issue returned as described at the beginning.
Who can explain this ? 😄
Then i removed the copy of one of the existing dbs, cleaned up everything in file system (db and logfiles), too. Restarted infostoreservice on "problem server", ensured the related ad object has been purged, too.
Only then i created a new fresh copy from "main server" (no issues there) to the "problem server" again. This way even the file/folder permissions have been created correctly. However, as soon as seeding of 300 GB was finished), the same issue returned as described at the beginning.
Who can explain this ? 😄
There are additional things to check.
If there is anything related to the event log of the problem server, I will check it.
If there is anything related to the event log of the problem server, I will check it.