Update Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 7s

This commit is contained in:
2025-07-05 16:02:11 -06:00
parent b9277ccd20
commit 88fe7d1f7b

View File

@ -9,6 +9,11 @@ Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, Re
```
| **Name** | **Status** | **CopyQueueLength** | **ReplayQueueLength** | **ContentIndexState** |
| :--- | :--- | :--- | :--- | :--- | :--- |
| `DB01\MX-DAG-01` | Mounted | 0 | 0 | Healthy |
| `DB01\MX-DAG-02` | Healthy | 0 | 0 | Healthy |
| :--- | ---: | ---: | ---: | ---: |
| 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