Topic Last Modified: 2010-11-12

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.

To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Object Name

MSExchange Active Manager

Counter Name

Database Mounted

Sample Interval

60

Server Role

Ex14. Mailbox

Rule Path

Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Mounted

Rule Name

The database copy is not mounted on the local server. Another database copy may be mounted on a different server.

Explanation

This alert indicates that an issue may affect a database on a Mailbox server in a particular Microsoft Exchange Server 2010 database availability group.

A database availability group (DAG) is a set of Mailbox servers that provide automatic recovery from failures that affect individual databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works together with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases.

Only one mailbox database may be the active copy at any one time. When the active mailbox database fails, a passive copy is mounted to become the active mailbox database. System Center Operations Manager monitors the mount operations to verify that a database copy has mounted successfully. An alert is generated when the database copy is not mounted successfully. This may indicate that a problem affects the database copy or that another copy has been mounted on another server in the DAG.

User Action

To resolve this error, do one or more of the following:

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

  • Examine the current replication status for each replica database. To do this, use the Get-MailboxDatabaseCopyStatus cmdlet. This cmdlet returns 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. For example:

    Copy Code 
     Get-MailboxDatabaseCopyStatus *
  • Examine the Services MMC on the servers in the DAG to verify that the Microsoft Exchange Information Store Service is running. Additionally, examine the Application logs on the servers determine whether the active mailbox database is dismounted. When the Information Store service is stopped gracefully, active database copies on the server are dismounted. In this scenario, the database instances do not fail over to other members of the DAG.

For more information, see the following topics in Exchange 2010 Help:

  • Understanding Mailbox Database Copies

  • Understanding Database Availability Groups

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.