Solutions > AppInsight Applications > Understanding AppInsight for Exchange > Mailbox Database Copies

Mailbox Database Copies

This resource shows the status of the Exchange mailbox database copies. The data can be sorted by clicking the headers of each column.

Hovering over any Database Name in the list displays detailed information about that database in the tooltip. Hovering over the node provides a tooltip with information about that node.

The following list defines each column of this resource:

  • Database Name: Name of the listed database copy.
  • Copy Status: Displays the status of the listed database copy. (See Table 1 below for possible statuses.)
  • Content Index State: See the following table for returned status descriptions. (See Table 2 below for possible statuses.)
  • Exchange Server: Name of the Exchange application and the node it is on.

Table 1.

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 has been 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 has been 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 Suspend-MailboxDatabaseCopy cmdlet.

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 will not periodically check whether the problem has been 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.

 

Table 2.

State

Description

Status on Active & Passive Copies

Crawling

Database is in the process of indexing database content. Depending on the size of the database, this process could take some time to complete.

Warning

Disabled

Indexing for the database has been disable by an administrator.

Offline (Active)
N/A (Passive)

Failed

An error has occurred causing the content index to fail.

Critical

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.

Critical

Healthy

This indicates the Content Index is up to date and has not detected any issues. This is the only state in which a failover (automatic process) to a specific database copy can occur. 

Up

Seeding

A database copy is in the process of updating its Content Index from another database copy.

Up

Suspended

The Suspended status occurs if an administrator manually pauses or suspends it from receiving updates from the active copy. This might be done to update a failed Content Index or to perform troubleshooting for other issues.

Warning