asked on

exchange 2007 database errors

my backup exec has started giving me fail statuses while backing up my exchange 2007 server:

WARNING: "\\MAIL3\Microsoft Information Store\Dreison\mdyne1" is a corrupt file.
This file cannot verify.

The db mounts properly, and eseutil /mk shows no errors. When I run eseutil /ml, however I get this error in the event log:

eseutil (2212) The log file D:\mailboxes\mdyne\mdyne1.edb is damaged, invalid, or inaccessible (error -514) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.

Backup exec goes ahead and backs the db up.

So, what do I do? I caught this too late to restore from a backup, or roll any good logs forward. Even though the db mounts properly, will eseutil /p help me in this situation? Is there any other way to get rid of the corrupt log files?

Rick Fee

First run eseutil /d and see if that solves it if not run /p....let me know how it turns out. Still a no go you might create a new db and move all mbx's to this new one and remove this damaged db.

ASKER CERTIFIED SOLUTION

daines

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

twinstead

ASKER

I will try both suggestions as soon as I can. Thanks.

So if I am able to successfully mount and dismount the database, there's a chance I can just dismount, move the logs, and then remount to at least fix the backup exec error? I'm fairly new to Exchange 2007, and this is the first time I've had any issues with my databases.

daines

Yup... The suggestion given above is to get rid of the log file error... I mean moving logs out after dismounting the database... This should fix the backup problem...

twinstead

ASKER

Sorry for the delay in responding gentlemen. Your suggestion worked well, daines. Thank you.