From 118a612132a7255a1b95f736c09e700880c2cb7d Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 5 Jul 2025 16:47:09 -0600 Subject: [PATCH] Update Servers/Microsoft Exchange/Scripts/DAG/Database Management.md --- Servers/Microsoft Exchange/Scripts/DAG/Database Management.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md index 0de0137..a448719 100644 --- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md +++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md @@ -53,6 +53,7 @@ Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -ReplicationOnly If you see this, it generally means that the Exchange Services for some reason or another are not running. You can remediate this with a 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`. [:material-powershell: Restart Exchange Services Script](https://docs.bunny-lab.io/Servers/Microsoft%20Exchange/Scripts/Restart%20Exchange%20Services/){ .md-button } + !!! 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.