JetError -501, JET_errLogFileCorrupt, Log file is corrupt

[vraengmose]

Hi Everyone,

I have been looking for a solution to my Veeam MS365 backup issue. I keep getting this error when running the backup task.
JetError -501, JET_errLogFileCorrupt, Log file is corrupt.

I see in the log:

Code: Select all

02-02-2024 09:22:19   26 (4088) Initializing database pool...
02-02-2024 09:22:19   26 (4088)  Time period per database file: 12 months
02-02-2024 09:22:19   26 (4088) Creating database context (D:\O365 Backup\2099)...
02-02-2024 09:22:19   26 (4088) Creating ESE instance VEEAM_ARCHIVER_PROXY_22119c8e-7c72-4139-9a43-ab98e4e6fd9b...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxVerPages to 1073741824...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxOpenTables to 15000...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxTemporaryTables to 1000...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxSessions to 1000...
02-02-2024 09:22:19   26 (4088)  Initializing ESE instance...
02-02-2024 09:22:19    4 (6476)  Service started
02-02-2024 09:22:19   26 (4088) Failed to refresh archive points versions: JetError -501, JET_errLogFileCorrupt, Log file is corrupt
02-02-2024 09:22:19   26 (4088) Creating database context (D:\O365 Backup\2099)...
02-02-2024 09:22:19   26 (4088) Creating ESE instance VEEAM_ARCHIVER_PROXY_9a0d3aa7-a59b-4bb0-8353-fc1845b18cc9...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxVerPages to 1073741824...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxOpenTables to 15000...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxTemporaryTables to 1000...
02-02-2024 09:22:19   26 (4088)  Setting instance parameter MaxSessions to 1000...
02-02-2024 09:22:19   26 (4088)  Initializing ESE instance...
02-02-2024 09:22:20   26 (4088) Failed to load repository (ID: 6263dd3a-11b0-4eff-885e-38d31b06b55b).
02-02-2024 09:22:20   26 (4088) Error: JetError -501, JET_errLogFileCorrupt, Log file is corrupt
02-02-2024 09:22:20   26 (4088) Type: Veeam.Jet.JetError

I have tjek all repository.adb an see all have a State: Clean Shutdown.

Anybody can point me a solution to this issue?

[Mildur]

Hi Thomas

Yes, please open a case with our customer support team. We cannot fix database files for you over a forum topic.
Technical issues always require a case with our support team. Please let me know the case number.
Forum policy: veeam-backup-replication-f2/rules-of-po ... -t755.html

May I ask what sort of storage have you in use to store backups for Veeam Backup for Microsoft 365. A corrupted database file generally means you are using an unstable storage solution for your backup repository. I see it's on Drive D. Is it a local disk, external USB drive or a network connected volume from a SAN appliance?

Best,
Fabian

[vraengmose]

Hi Fabian,

The disk is was on a ISCSI connection and i believe the issue happened after the server was reverted to an earlier snapshot.
The licenses is a Veeam community licens, I'm a little unsure if it's possible to get support.

[Mildur]

As a community edition user, you are eligible to open a support case. Response time is on best effort. Which means, if our support engineers have free capacity, they will take over cases from our free users as well.

The disk is was on a ISCSI connection and i believe the issue happened after the server was reverted to an earlier snapshot of the server.

I suspect that reverting the snapshot did not result in a clean shutdown of the operating system. Resetting the server without a proper shutdown could potentially lead to corruption of the filesystem on the iSCSI volume and the database. Corrupted jet db files sometimes can be repaired with the eseutil command. But I cannot provide you guidance on how to use it safely. A support case is required for the command.

May I ask about the reason for reverting the snapshot? Were there any issues with Windows updates? It is possible that during the update process, the jet database driver in the operating system was updated, consequently upgrading the database to a newer version. Reverting the server to a previous state with an older version of the jet database driver would render the database un-mountable as well.

Best,
Fabian

[vraengmose]

Glad that is an option. But where do we raise a community edition support ticket?

The server was reverted do to a other issue and there was not taken in consideration the "Veeam Backup for Microsoft 365" was running.

[Gostev]

veeam.com/support

Although this support team is overloaded these days due to cases resulting from constant API changes on M365 side in the past weeks, so don't hold your hopes too high. It is unlikely they will a have spare capacity currently to take on the issue as complex as this one for a non-paying user...

[vraengmose]

We have deside to start a fresh backup instead. Thanks for you help and have a great weekend!