From 61f0d1ae5bbd8252daad835b81873db78f86b277 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 5 Jul 2025 16:42:58 -0600 Subject: [PATCH] Update Servers/Microsoft Exchange/Scripts/DAG/Database Management.md --- .../Microsoft Exchange/Scripts/DAG/Database Management.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md index c92d4bd..95b0aa9 100644 --- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md +++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md @@ -49,6 +49,12 @@ If this fails to cause replication to resume, you can try telling the database t Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -ReplicationOnly ``` +### If `Status` is `ServiceDown` +If you see this, it generally means that the Exchange Services for some reason or another are not running. You can remediate this with an [Restart Exchange Services](https://docs.bunny-lab.io/Servers/Microsoft%20Exchange/Scripts/Restart%20Exchange%20Services/) powershell script. You will then have to double-check your work to ensure that all "Microsoft Exchange" services that have a startup mode of "Automatic" are running, if not, manually start them, then check on the status of the DAG again to see if the status changes from `ServiceDown` to `Healthy`. + +!!! info "Be Patient` + Depending on the speed of the Exchange server, it may take a few minutes, 5-10 minutes, for the services to fully initialize and be ready to handle requests. Go get a coffee and come back and check on the status of the DAG at that time. + ### If `ContentIndexState` is Unhealthy or Suspended If you see that the "ContentIndexState" is unhappy, you can run the following command to force it to re-seed / rebuild itself. (This is non-destructive this this is happening on a replica database). ```powershell