Solutions > AppInsight Applications > Understanding AppInsight for Exchange > Replication Status Checks

Replication Status Checks

This resource performs up to 16 checks in Exchange 2010 and up to 18 checks in Exchange 2013 (divided into two columns. This resource only shows test results which apply to the server it is being run against, whether the server contains only active databases, passive databases, or a combination of the two. The fewest checks are performed when run against a server with only active databases (Seven checks for 2010, 12 checks for 2013). This is because check for databases replication status is not necessary because they are all on the local server.

The status for each Health Check Test can be one of the following: Passed, Failed, or Warning.

The table below provides a list of all possible tests for this resource along with their definitions.

Health Check Test Name Description

TcpListener

Verifies that the TCP log copy listener is running and reachable on the specified DAG member, or if no DAG member is specified, on the local server.

TasksRpcListener

Verifies that the tasks remote procedure call (RPC) server is running and reachable on the specified DAG member, or if no DAG member is specified, on the local server.

ServerLocatorService

Verifies the Active Manager client/server processes on DAG members and on the Client Access Server that perform lookups in Active Directory and Active Manager to determine where a user’s mailbox database is active.

ReplayService

Verifies that the Microsoft Exchange Replication service is running and reachable on the specified DAG member, or if no DAG member is specified, on the local server.

QuorumGroup

Verifies that the default cluster group (quorum group) is in a healthy and online state.

FileShareQuorum

Verifies that the witness server and witness directory and share configured for the DAG are reachable.

DBLogReplayKeepingUp

Verifies that replay activity for the passive copies of databases on the specified DAG member, or if no DAG member is specified, on the local server, is able to keep up with log copying and inspection activity.

DBLogCopyKeepingUp

Verifies that log copying and inspection by the passive copies of databases on the specified DAG member, or if no DAG member is specified, on the local server, are able to keep up with log generation activity on the active copy.

DBInitializing

Checks whether any mailbox database copies are in a state of Initializing on the specified DAG member, or if no DAG member is specified, on the local server.

DBDisconnected

Checks whether any mailbox database copies are in a state of Disconnected on the specified DAG member, or if no DAG member is specified, on the local server.

DBCopySuspended

Checks whether any mailbox database copies are in a state of Suspended on the specified DAG member, or if no DAG member is specified, on the local server.

DBCopyFailed

Checks whether any mailbox database copies are in a state of Failed on the specified DAG member, or if no DAG member is specified, on the local server.

DatabaseRedundancy (Only 2013)

Verifies that there is at least one healthy copy available of the databases on the specified DAG member, or if no DAG member is specified, on the local server.

DatabaseAvailability (Only 2013)

Verifies that the databases have sufficient availability on the specified DAG member, or if no DAG member is specified, on the local server.

DagMembersUp

Verifies that all DAG members are available, running, and reachable.

ClusterService

Verifies that the Cluster service is running and reachable on the specified DAG member, or if no DAG member is specified, on the local server.

ClusterNetwork

Verifies that all cluster-managed networks on the specified DAG member, or if no DAG member is specified, the local server, are available.

ActiveManager

Verifies that the instance of Active Manager running on the specified DAG member, or if no DAG member is specified, the local server, is in a valid role (primary, secondary, or stand-alone).