Another way to get a quick overview of the replication status of your mailbox database copies is to use the Test-ReplicationHealth cmdlet.
When you run this cmdlet, specify the mailbox server that should be tested, as shown in the following screenshot:
As you can see from the output, all of the cluster services and resources are tested. In addition, several aspects of database copy health will be checked, including log replay, log copy queues, and the status of the database, as well as whether it is suspended, disconnected, or initializing.
To proactively monitor replication health on an ongoing basis, you can schedule the ...
