If you don’t set up a database availability group, you could ignore the errors safely. The database redundancy and availability checks ensure that you have more than one copy of the database configured and that those copies are healthy. If the database redundancy and availability checks fail, it intends that the database in error is not configured to have more than one copy. For the databases with multiple copies, you could check the reason for failure by checking the detailed status of each component provided by the cmdlet.
Exchange 2016 CU23 and problems with DatabaseRedundancy and DatabaseAvailability
Hello,
I have a standalone exchange server 2016 with CU 23 and I have problems. Sending e-mails takes a very long time, even several dozen minutes.
A few days ago exchange start having problems with this:
When I look at errors I've got this for DatabaseRedundancy :
And for DatabaseAvailability:
Any ideas for it?
Exchange | Exchange Server | Other
Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Windows for business | Windows Server | User experience | Other
1 additional answer
Sort by: Most helpful
-
Xuyan Ding - MSFT 7,601 Reputation points
2023-04-14T07:22:14.74+00:00 Hi @drClays ,
As Amit Singh said, if you don’t set up a database availability group, you could ignore the errors safely.
I tested my Exchange lab without DAG, it returns the same result.For slow mail sending, you can check the mail queue for stuck mail. Open Exchange Toolbox and select Queue Viewer. View email details through the "Queue Viewer". In the list of messages in the queue, you can view detailed information about each email, including its status, recent events, and error characters.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.