From 2f98f8c95e57192d9633022b78bdc4e26f61ef26 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 5 Jul 2025 16:05:43 -0600 Subject: [PATCH] Update Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md --- .../Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md b/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md index baf4541..996c49c 100644 --- a/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md +++ b/Servers/Microsoft Exchange/Scripts/DAG/Reseed Replica Database.md @@ -16,4 +16,6 @@ Get-MailboxDatabaseCopyStatus * | Format-Table Name, Status, CopyQueueLength, Re !!! note "Example Output Breakdown" In the above example output, you can see that there are two member servers in the DAG, `MX-DAG-01` and `MX-DAG-02`. Then you will see that there is a status of `Mounted`, this means that `MX-DAG-01` is the active production server; this means that it is handling all mailflow and web requests / webmail. - **CopyQueueLength**: This is the queue of all database transactions that are being copied from the production (mounted) database to replica databases. This number can grow quite fast and should be \ No newline at end of file + **CopyQueueLength**: This is a number of database "*transaction logs*" that have taken place since a replica database stopped getting updates. This is the queue of all database transactions that are being copied from the production (mounted) database to replica databases. This data is not immediately written to the replica database(s). + + **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 dropping. \ No newline at end of file