Nicole Rappe
88fe7d1f7b
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 7s
19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
### Purpose
|
|
If you operate an Exchange Database Availability Group (DAG) with 2 or more servers, you may need to do maintenance to one of the members, and during that maintenance, it's possible that one of the databases of the server that was rebooted etc will be out-of-date. In case this happens, it may suspend the database replication to one of the DAG's member servers.
|
|
|
|
### Checking DAG Database Replication Status
|
|
You will want to first log into one of the DAG servers and open the *"Exchange Management Shell"*. From there, run the following command to get the status of database replication. An example of the kind of output you would see is below the command.
|
|
|
|
```powershell
|
|
Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, ReplayQueueLength, ContentIndexState
|
|
```
|
|
|
|
| **Name** | **Status** | **CopyQueueLength** | **ReplayQueueLength** | **ContentIndexState** |
|
|
| :--- | ---: | ---: | ---: | ---: |
|
|
| DB01\MX-DAG-01 | Mounted | 0 | 0 | Healthy |
|
|
| DB01\MX-DAG-02 | Healthy | 0 | 0 | Healthy |
|
|
|
|
!!! note "Example Output Breakdown"
|
|
In the above example output, you can see that there are two member servers in the DAG, `MX-DAG-01` and `MX-DAG-02`. Then you will see that there is a status of `Mounted`, this means that `MX-DAG-01` is the active production server; this means that it is handling all mailflow and web requests / webmail.
|
|
|
|
**CopyQueueLength**: This is the queue of all database transactions that are being copied from the production (mounted) database to replica databases. This number can grow quite fast and should be |