From 8a816f20483bc36bcd8369600b0fa9ad2651cfe3 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 5 Jul 2025 16:30:14 -0600 Subject: [PATCH] Update Servers/Microsoft Exchange/Scripts/DAG/Database Management.md --- .../Scripts/DAG/Database Management.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md index 11c47f2..84804ee 100644 --- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md +++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md @@ -25,7 +25,7 @@ Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, Re ### Troubleshooting You may run into issues where either the `Status` or `ContentIndexState` are either Unhealthy, Suspended, or Failed. If this happens, you need to resume replication of the database from the production active/mounted server to the server that is having issues. In the worst-case, you would re-seed the replica database from-scratch. -### If `Status` is Unhealthy +### If `Status` is Unhealthy or Suspended If one of the DAG members has a status of "**Unhealthy**", you can run the following command to attempt to resume replication. ```powershell Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" @@ -41,3 +41,12 @@ If you see that the "ContentIndexState" is unhappy, you can run the following co ```powershell Update-MailboxDatabaseCopy "DB01\MX05" -CatalogOnly -BeginSeed ``` + +### If Replica Database is FUBAR +If the replica database just is not playing nice, you can take the *nuclear option* of completely rebuilding the replica database. + +!!! warning + This will destroy the replica database, so be careful to ensure you have a backup (if possible) before you do this. The following command will replicate the data from the production active/mounted database to the replica database. + ```powershell + Update-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -SourceServer "MX-DAG-01" + ```