-501 (logfile corrupt) on some Exchange databases

[MaxPlanck]

Hey guys,

we are currently in trouble with our Exchange 2010 SP1 backup.

We run 2 Mailbox roles, that both have 3 mailbox databases (db01, db02, db03), in a DAG setup. Backup Exec agents are deployed on all Exchange Servers (currently in version 13.0.2896).

Backup Exec is currently version 2010 R2.

When we run a backup job, one or two of our databases fail with the -501 error, stating the log file is corrupt:

Error message (sorry, it's in german): Sichern- \\DAG2010\Microsoft Information Store\DB01V-79-57344-759 - Der Vorgang für die ausgewählte Ressource unter Verwendung der angegebenen Optionen konnte nicht abgeschlossen werden. Beim Öffnen der Exchange-Datenbankdatei wurde der folgende Fehler ausgegeben: "-501 The log file is corrupt. "

The backup job settings look like this:

I did a check on the failed logfiles of db01 with eseutil /ml that succeeded on all log files, but returned an error on E01.log:

ERROR: Cannot open log file (E:\Protokoll\DB01\E01.log). Error -1032.

Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 36.656 seconds.

There are also no events (warnings or errors) listed on our Exchange Servers, that correspond to the backup job.

When we exclude DB01, and backup only DB02, the backup job finishes successfully.

Turning off GRT, which might work according to some other posts, is not an option really.

Any ideas?

Thanks in advance!

[CraigV · Accepted solution]

Hi there,

2 things to try:

1. If you're running AOFO on your job, turn it off as this isn't recommended.

2. Upgrade to BE 2010 R3 and run LiveUpdate to patch with all available updates. Once done, push-install to any remote servers and try the backup again...

Thanks!

[MaxPlanck]

Hi,

thanks for your quick reply.

We have AOFO disabled for this job, but, we were not aware about R3, so we'll do an update and get back to you!

Thanks for pointing this out!

Regards