![]() ![]() ![]() ![]() The mailbox database copy is being seeded, the content index for the mailbox database copy is being seeded, or both are being seeded. ![]() After the system has detected that the problem is resolved, and barring no other issues, the copy status will automatically change to Healthy. While in a Failed state and not suspended, the system will periodically check whether the problem that caused the copy status to change to Failed has been resolved. The mailbox database copy is in a Failed state because it isn't suspended, and it isn't able to copy or replay log files. Database copy status Database copy status The following table describes possible values for the copy status of a mailbox database copy. This cmdlet enables you to view information about all copies of a particular database, information about a specific copy of a database on a specific server, or information about all database copies on a server. You can use the Get-MailboxDatabaseCopyStatus cmdlet to view status information about mailbox database copies. You can use the details in this topic for monitoring the health and status of mailbox database copies for database availability groups (DAGs), for gathering diagnostic information, and for configuring the low disk space monitoring threshold. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |