Copy Status
| Description
|
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 will remain 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 will remain 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 will periodically check 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 will automatically change 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.
|
Content Index 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
|
CopyQueueLength
| Definition:
Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy isn't considered complete until it has been checked for corruption.
Information:
All nodes in a Database Availability Group (DAG) should be monitored for this counter depending on the passive node. Should be less than 1 at all times for continuous replication.
Possible problems:
Server recently rebooted or services restarted, network connectivity issues, or multiple mailbox moves are in process.
Remediation:
Verify network connectivity between the various nodes in the DAG. Verify Replication Service is running on all DAG members.
| > 1
| > 1 for 5 polls
|
ReplayQueueLength
|
Definition:
Shows the number of transaction log files waiting to be replayed into the passive copy.
Information:
With DAG replication, transaction logs are shipped to the other DAG members. They then replay the log file. (Thresholds should be manually removed for DAG members configured to be 'lagged copies.')
Possible problems:
The replay queue length should be as low as possible, otherwise this could indicate a (performance) issue with the DAG member containing the Copy database. A high number could also negatively affect failover with some loss of data as a possibility.
Remediation:
Check Memory, CPU, and Disk I/O for any bottlenecks. Review the Windows Event logs for any related events.
- Replay queue length Indicates the number of log files waiting to be replayed into the selected database copy. This field is relevant only for passive database copies.
- Replay queue length (logs) Indicates the number of log files waiting to be replayed into this copy of the database.
With DAG replication, transaction logs are shipped to the other DAG members. They then replay the log file. It contains all the database changes performed on the Active database. Replay means that these changes are then also performed on the Copy databases exactly as they were on the Active database.
The replay queue length should be as low as possible, otherwise this could indicate a (performance) issue with the DAG member containing the Copy database. A high number could also negativly affect failover with some dataloss as a possibility.
| > 50 for 5 polls
| > 100 for 5 polls
|
Avg Log Copy Latency (msec)
(Only available in Exchange 2010)
| Definition:
Average number of milliseconds observed by the log copier when sending messages over the network.
| N/A
| N/A
|
Log Copy KB/sec
| Definition:
The size of the log files (in KB) that are copied per second.
Information:
Shows the size in KB/sec of the transaction logs being copied to passive copies.
| N/A
| N/A
|
Log Replay Rate (generations/sec)
| Definition:
The number of log files that have been replayed per second.
Information:
Shows you the number of Transaction Logs being replayed on the passive copies of a database.
| N/A
| N/A
|
Log Replay is Not Keeping Up
| Definition:
LogReplayNotKeepingUp is 1 when log replay is falling behind and not able to keep up with log copying and inspection.
Information:
Exchange 2010/2013 uses continuous replication to create and maintain database copies. To maintain a synchronized copy of a mailbox database, transaction log files from the active mailbox server are replayed into the passive database of another server in the DAG. This provides high availability and resiliency in the Exchange environment.
Possible problems:
Indicates a replication issue may exist with the mailbox database copies in the DAG. If Transaction Log replay is not able to keep up with the active copy, passive copies will not be up of date.
Remediation:
Review the Windows Event logs for any related events. Examine network topology between DAG members and verify connectivity and network latency is below 250 ms. Examine CPU utilization by the Information Store service on passive copies. Examine the replication status for each replica database using the Get-MailboxDatabaseCopyStatus cmdlet.
| >= 1
| >= 1 for 60 polls
|
AutoDatabaseMountDial的設定為GoodAvailability，AutoDatabaseMountDial參數可允許的copy queue length長度如下：
QQ群⑧：
窥视卡
雷达卡
发表于 2017-12-8 18:27:21
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
千斤顶
显身卡