I have an issue with Exchange 2016 creating DAG databases. I create the database on the first server, and mount it. The content index stays in the failed mode for a little while, but then goes into a healthy state. I then tell it to create a databasecopy to another DAG member. The database mounts on server 2, but the index stays in a failed mode for a while (5+ minutes) and goes into a failed suspend mode, and stays there.
I have had this happen with multiple databases. I have seen a couple of threads (google searches) on this for 2016, and 2013. One suggested creating a special group in AD. (Done). Others suggest changing the mount priority on the databases. Huh? This is very odd. Anybody else seeing this out there? Any known fixes? Thanks Steven Stringham ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. ยง2510-2521.
