Veeam Microsoft 365 Community Edition Corrupt adb.log file corrupt.
Does anyone know how to fix corrupt adb.log files?
I already submitted a ticket but since its the Community Edition, I doubt I will get assistance.
Solved
Veeam Microsoft 365 Community Edition Corrupt adb.log file corrupt
Best answer by anthonysaulnier
adb.log is part of the Jet (ESE) transaction log used by the Veeam M365 repository database.
Disable all the Veeam services and try to run soft recovery to replay the transaction logs into the database:
eseutil /r adb /l "<log folder path>" /d "<database folder path>"
Then check the database state to see if it’s Clean Shutdown
eseutil /mh repository.adb
If logs are too damaged to replay, you can run a hard repair:
eseutil /p "<database path\repository.adb>”
This should allow the database to mount again if the corruption is limited to the transaction logs.
Thank you for your reply. Sorry I just seen your message now. I didn’t get any support from Veeam and they closed my ticket. I will definitely make note of this in case I run into problems again in the future.
In the meantime I created another repository, but left the old repository folder in place, and left the repository entry in place as well in Veeam and created a new one.
But I am certainly going to make note of your suggestion.
Thanks again.
+21You are best to wait on support but this might help - https://satheesh.net/2021/05/veeam-backup-for-microsoft-office-365-jeterror-501-jet_errlogfilecorrupt-log-file-is-corrupt/
+1Veeam describe the support model for the community edition as best effort with no Service level agreements.
what this means in reality is, support will eventually answer your question, but they only when they aren't dealings with higher priority or paid support tickets.
You are best to wait on support but this might help - https://satheesh.net/2021/05/veeam-backup-for-microsoft-office-365-jeterror-501-jet_errlogfilecorrupt-log-file-is-corrupt/
Thanks, this is some great information to have. I did go through this and check that the repository itself is fine but the issue is the log file itself.
[07.03.2026 00:00:02.160] 3 (6) [Info] Invalid repository status is returned (repository ID: 2d501c21-62e3-46c0-a0e7-2b4970a33307, is outdated: False, is out of sync: False, is out of order: True, out of order reason: JetError -501, JET_errLogFileCorrupt, Log file is corrupt)
I run the backups once a day to SATA platter style (non solid state) drive. I’m wondering if the file is fragmented and if I should be moving to a solid state drive.
+21You are best to wait on support but this might help - https://satheesh.net/2021/05/veeam-backup-for-microsoft-office-365-jeterror-501-jet_errlogfilecorrupt-log-file-is-corrupt/
Thanks, this is some great information to have. I did go through this and check that the repository itself is fine but the issue is the log file itself.
[07.03.2026 00:00:02.160] 3 (6) [Info] Invalid repository status is returned (repository ID: 2d501c21-62e3-46c0-a0e7-2b4970a33307, is outdated: False, is out of sync: False, is out of order: True, out of order reason: JetError -501, JET_errLogFileCorrupt, Log file is corrupt)
I run the backups once a day to SATA platter style (non solid state) drive. I’m wondering if the file is fragmented and if I should be moving to a solid state drive.
Moving to SSD would help for sure.
+2adb.log is part of the Jet (ESE) transaction log used by the Veeam M365 repository database.
Disable all the Veeam services and try to run soft recovery to replay the transaction logs into the database:
eseutil /r adb /l "<log folder path>" /d "<database folder path>"
Then check the database state to see if it’s Clean Shutdown
eseutil /mh repository.adb
If logs are too damaged to replay, you can run a hard repair:
eseutil /p "<database path\repository.adb>”
This should allow the database to mount again if the corruption is limited to the transaction logs.
adb.log is part of the Jet (ESE) transaction log used by the Veeam M365 repository database.
Disable all the Veeam services and try to run soft recovery to replay the transaction logs into the database:
eseutil /r adb /l "<log folder path>" /d "<database folder path>"
Then check the database state to see if it’s Clean Shutdown
eseutil /mh repository.adb
If logs are too damaged to replay, you can run a hard repair:
eseutil /p "<database path\repository.adb>”
This should allow the database to mount again if the corruption is limited to the transaction logs.
Thank you for your reply. Sorry I just seen your message now. I didn’t get any support from Veeam and they closed my ticket. I will definitely make note of this in case I run into problems again in the future.
In the meantime I created another repository, but left the old repository folder in place, and left the repository entry in place as well in Veeam and created a new one.
But I am certainly going to make note of your suggestion.
Thanks again.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.