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?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
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.

Dismount the database. Move out all the log files .

 When you dismount the database it will replay all existing logs into the database, therefore when you move the logs, you will not be loosing any information.

Now mount the database again. Try to take a backup again & let me know the results.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
twinsteadAuthor Commented:
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.

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...
twinsteadAuthor Commented:
Sorry for the delay in responding gentlemen. Your suggestion worked well, daines. Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.