Database Details
This widget provides details concerning the current database.
The following list defines each field of this widget:
- Database Name: This provides the name of the current database.
- Summary Status: Displays the current status of the database. (See Table 1 for possible statuses.)
- Active Copy Status: Displays the current status of the database of the Exchange application that is being monitored. (See Table 2 for possible statuses.)
- Preferred Server: The database copy with an activation preference of 1 is the preferred server.
- Master: This refers to the name of the DAG or the name of the Server which maintains the copy status information.
- Total Number of Mailboxes: Displays the total number of mailboxes on the listed database.
- Average Mailbox Size: Displays the average size of user mailboxes.
- Last Full Backup: Displays the time and date of the last full backup of the database.
- Last Incremented Backup: Displays the time and date of only those files that were altered since the last full backup of the database.
- Circular Logging: Circular logging is a method of conserving disk space by deleting transaction log files after they have been committed to the database. Circular Logging should only be enabled if the mailbox server is part of a DAG with a minimum of three database copies and one of those should be set as a "lagged copy."
- Storage Quota Defaults:
- Issue Warning: Displays the minimum size the mailbox must be before a Warning is issued to the user's mailbox.
- Prohibit Send: Displays the minimum size the mailbox must be before sending email is prohibited from the user's mailbox.
- Prohibit Send and Receive: Displays the minimum size the mailbox must be before sending and receiving email is prohibited from the user's mailbox.
Table 1.
This table shows how the value for the Summary Status field is calculated. If the conditions in the first four columns are met, the status in the Final SAM Status column is displayed in the Summary Status field.
DB Copy Status (Active) | DB Copy Status (Passive) | DB Content Index State (Active) | DB Content Index State (Passive) | Final SAM Status |
---|---|---|---|---|
Dismounted |
Any |
Any |
Any |
Offline |
Dismounting |
Any |
Any |
Any |
Warning |
Failed |
Any |
Any |
Any |
Down |
Initializing |
Any |
Any |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
DisconnectedAndHealthy |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
DisconnectedAndHealthy |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
DisconnectedAndResynchronizing |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
DisconnectedAndResynchronizing |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
Failed |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Failed |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
FailedAndSuspended |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
FailedAndSuspended |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
Healthy |
Healthy, Seeding, or SeedingSource |
Healthy, Seeding, or SeedingSource |
Up |
Mounted, Seeding, or SeedingSource |
Healthy |
Healthy, Seeding, or SeedingSource |
Any other |
Warning |
Mounted, Seeding, or SeedingSource |
Healthy |
Crawling |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Healthy |
Any other |
Healthy, Seeding, or SeedingSource |
Warning |
Mounted, Seeding, or SeedingSource |
Healthy |
Any other |
Any other |
Critical |
Mounted, Seeding, or SeedingSource |
Initializing |
Healthy, Seeding, or SeedingSource |
Any |
Up |
Mounted, Seeding, or SeedingSource |
Initializing |
Any other |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Resynchronizing |
Healthy, Seeding, or SeedingSource |
Healthy, Seeding, or SeedingSource |
Up |
Mounted, Seeding, or SeedingSource |
Resynchronizing |
Healthy, Seeding, or SeedingSource |
Any other |
Warning |
Mounted, Seeding, or SeedingSource |
Resynchronizing |
Any other |
Healthy, Seeding, or SeedingSource |
Warning |
Mounted, Seeding, or SeedingSource |
Resynchronizing |
Any other |
Any other |
Critical |
Mounted, Seeding, or SeedingSource |
Seeding |
Healthy, Seeding, or SeedingSource |
Any |
Up |
Mounted, Seeding, or SeedingSource |
Seeding |
Any other |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
SeedingSource |
Healthy, Seeding, or SeedingSource |
Any |
Up |
Mounted, Seeding, or SeedingSource |
SeedingSource |
Any other |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Service Down |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Service Down |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
SinglePageRestore |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
SinglePageRestore |
Any other |
Any |
Critical |
Mounted, Seeding, or SeedingSource |
Suspended |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
Mounted, Seeding, or SeedingSource |
Suspended |
Any other |
Any |
Critical |
Mounting |
Any |
Any |
Any |
Warning |
Service Down |
Any |
Any |
Any |
Down |
SinglePageRestore |
DisconnectedAndHealthy |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
DisconnectedAndHealthy |
Any other |
Any |
Critical |
SinglePageRestore |
DisconnectedAndResynchronizing |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
DisconnectedAndResynchronizing |
Any other |
Any |
Critical |
SinglePageRestore |
Failed |
Any |
Any |
Critical |
SinglePageRestore |
FailedAndSuspended |
Any |
Any |
Critical |
SinglePageRestore |
Healthy |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
Healthy |
Crawling |
Any |
Critical |
SinglePageRestore |
Healthy |
Any other |
Any |
Critical |
SinglePageRestore |
Initializing |
Any |
Any |
Critical |
SinglePageRestore |
Resynchronizing |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
Resynchronizing |
Any other |
Any |
Critical |
SinglePageRestore |
Seeding |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
Seeding |
Any other |
Any |
Critical |
SinglePageRestore |
SeedingSource |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
SeedingSource |
Any other |
Any |
Critical |
SinglePageRestore |
Service Down |
Any |
Any |
Critical |
SinglePageRestore |
SinglePageRestore |
Any |
Any |
Critical |
SinglePageRestore |
Suspended |
Healthy, Seeding, or SeedingSource |
Any |
Warning |
SinglePageRestore |
Suspended |
Any other |
Any |
Critical |
Table 2.
Mounted |
The active copy is online and accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Mounted. |
Mounting |
The active copy is coming online and not yet accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Mounting. |
Dismounting |
The active copy is going offline and terminating client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounting. |
Dismounted |
The active copy is offline and not accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounted. |
Seeding |
The mailbox database copy is being seeded, the content index for the mailbox database copy is being seeded, or both are being seeded. Upon successful completion of seeding, the copy status should change to Initializing. |
Seeding Source |
The mailbox database copy is being used as a source for a database copy seeding operation. |
Initializing |
The mailbox database copy is in an Initializing state when a database copy is created, when the Microsoft Exchange Replication service is starting or has just been started, and during transitions from Suspended, Service Down, Failed, Seeding, or Single Page Restore to another state. While in this state, the system is verifying that the database and log stream are in a consistent state. In most cases, the copy status remains in the Initializing state for about 15 seconds, but in all cases, it should generally not be in this state for longer than 30 seconds. |
Re-synchronizing |
The mailbox database copy and its log files are being compared with the active copy of the database to check for any divergence between the two copies. The copy status remains in this state until any divergence is detected and resolved. |
Single Page Restore |
This state indicates that a single page restore operation is occurring on the mailbox database copy. |
Failed |
The mailbox database copy is in a Failed state because it is not suspended, and it is not able to copy or replay log files. While in a Failed state and not suspended, the system periodically checks whether the problem that caused the copy status to change to Failed was resolved. After the system has detected that the problem is resolved, and barring no other issues, the copy status automatically changes to Healthy. |
Service Down |
The Microsoft Exchange Replication service is not available or running on the server that hosts the mailbox database copy. |
Suspended |
The mailbox database copy is in a Suspended state as a result of an administrator manually suspending the database copy by running the |
Healthy |
The mailbox database copy is successfully copying and replaying log files, or it has successfully copied and replayed all available log files. |
Disconnected and Healthy |
The mailbox database copy is no longer connected to the active database copy, and it was in the Healthy state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy. |
Disconnected and Re-synchronizing |
The mailbox database copy is no longer connected to the active database copy, and it was in the Re-synchronizing state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy. |
Failed and Suspended |
The Failed and Suspended states have been set simultaneously by the system because a failure was detected, and because resolution of the failure explicitly requires administrator intervention. An example is if the system detects unrecoverable divergence between the active mailbox database and a database copy. Unlike the Failed state, the system does not periodically check whether the problem was resolved, and automatically recover. Instead, an administrator must intervene to resolve the underlying cause of the failure before the database copy can be transitioned to a healthy state. |