This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 3%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
How many log files failing to replicate between the active and passive copies of an Exchange Server 2019 database will trigger a full reseed?
A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello, @Krismayanto
It's been a long time since I've heard from you, have you solved your problem yet? Did my previous reply help you？ If it was useful, you can mark it as an answer. Thank you for your understanding and support.
Hi Jing, I believe the 3x 15 minutes applies if we enable Auto reseed, which is a new feature. My Exchange DBs without Auto reseed feature can still resume replication even after being suspended for a few hours, for example due to Network issue between sites.
Hi,@Krismayanto
Thanks for posting your question in the Microsoft Q&A forum.
Triggering AutoReseed is not determined by the number of replication log file failures, but by the fact that the database replica has been in the FailedandSuspended state for 15 consecutive minutes.
You can refer to this official document for details:https://learn.microsoft.com/en-us/exchange/high-availability/database-availability-groups/autoreseed?view=exchserver-2019&source=recommendations
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 98%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Agree with Bruce points, if database is in a FailedAndSuspended state. That said, if logs aren’t replicating properly, you can check with following command:
Get-MailboxDatabaseCopyStatus *
If AutoReseed isn’t working as expected, you can manually reseed the Exchange database.
Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Hi Jing, I believe the 3x 15-minute rule applies if we enable AutoReseed, which is a new feature. My Exchange databases can still resume replication even after being suspended for a few hours, for example, due to a network issue between sites
Hi Amit, the problem is not about the state, or how to check the status. Sometimes the replication suspended for a few hours (more than 3x 15 mins) because of network issue between sites. Sometimes it can resume, but sometimes we need to Update/Full reseed the DB. Question is what condition will requires full reseed.
hi，@Krismayanto
Some common scenarios that require a full reseed include: • Corruption or loss of the passive database copy – If the database file on a passive server becomes corrupted, deleted, or otherwise unusable, incremental log replay isn’t possible and a full reseed is needed.
• Log chain breakage – When there’s a break in the log chain (for example, if the necessary log files have been deleted, truncated, or are missing due to disk issues or configuration errors), the passive copy cannot catch up incrementally. A full reseed is required to re-establish the correct sequence.
• Extended downtime – If a passive copy has been offline for an extended period, the log files required to bring it up to date might no longer be available. In that case, you must perform a full reseed from the active copy.
• Configuration changes – In some cases, such as after certain upgrades or significant changes to the database, the passive copy might not be compatible with the active copy’s state. Though less common, this might also lead to a full reseed requirement.
In summary, any situation where the passive mailbox database copy can’t apply the incremental log changes due to data corruption, missing logs, or an incompatible state will require a full reseed to ensure the copy is valid and synchronized with the active database.
Hello, @
It's been a long time since I've heard from you, have you solved your problem yet? Did my previous reply help you？ If it was useful, you can mark it as an answer. Thank you for your understanding and support.