bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Nicole Rappe
2025-07-05 15:54:12 -06:00
parent 3e01f95a15
commit d05c04e2fa
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md Normal file
View File

@ -0,0 +1,15 @@
### 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:
```powershell
Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, ReplayQueueLength, ContentIndexState
```
!!! example "Example Output"
| **Name** | **Status** | **CopyQueueLength** | **ReplayQueueLength** | **ContentIndexState** |
| :--- | :--- | :--- | :--- | :--- | :--- |
| DB01\MX01 | Mounted | 0 | 0 | Healthy |
| DB01\MX02 | Healthy | 0 | 0 | Healthy |