From 2153244dbb397ddbae2e056e19fde226aaf3b36b Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 5 Jul 2025 16:23:35 -0600 Subject: [PATCH] Update Servers/Microsoft Exchange/Scripts/DAG/Database Management.md --- ...eplica Database.md => Database Management.md} | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) rename Servers/Microsoft Exchange/Scripts/DAG/{Reseed Replica Database.md => Database Management.md} (68%) diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md similarity index 68% rename from Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md rename to Servers/Microsoft Exchange/Scripts/DAG/Database Management.md index db81d41..28a1dd1 100644 --- a/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md +++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md @@ -20,4 +20,18 @@ Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, Re **CopyReplayLength**: This represents the queue of all data that was successfully copied from the production database to the replica database on the given DAG member that still needs to process on the replica database. The "**CopyQueueLength**" will need to reach zero before the "**CopyReplayLength**" will start making meaningful progress to reaching zero. - When both the "**CopyQueueLength**" and "**CopyReplayLength**" queues have reached zero, the replica database(s) will have reached 100% parity with the production (active/mounted) database. \ No newline at end of file + When both the "**CopyQueueLength**" and "**CopyReplayLength**" queues have reached zero, the replica database(s) will have reached 100% parity with the production (active/mounted) database. + +### 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 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" +``` + +If this fails to cause replication to resume, you can try telling the database to just focus on replication, which tells it to copy the queues and replay them on the replica database, while avoiding interacting with the "**ContentIndexState**" which can be individually fixed in the commands below: +```powershell +Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -ReplicationOnly +Update-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -CatalogOnly -BeginSeed