Exchange 2010 backup failing, corrupt log file/s

Yaayuh!

Yaayuh!

Yaayuh!

Soldato
Joined
5 Nov 2010
Posts
24,582
Location
Hertfordshire
Hi all, i think i have the fix for this but just wanted to run it by you guys and see if you have any alternatives.

Backup Exec 2010 throws this up after full backup every day:

"The consistency check of the snapshot for the microsoft exchange transaction log has failed"

"WARNING: "\\***********\Microsoft Information Store\*** Mailbox Database\Logs ( E010007118B.log - E0100072BA6.log )" is a corrupt file. This file cannot verify."
Click to expand...

The log files are not being cleaned up either.

This is the fix i have:

Dismount the database
Move log files
Remount database

From TechNet and confirmed via a few Google hits.

Anybody else had this issue?
 
I've had corrupt log file issues recently in my development domain for Exchange. Turns out that the storage unit RAID disks were causing it, even though there were no errors presented to me anywhere. I was just seeing errors with Exchange not mounting DB's due to corruptions. When I tried to browse to the data volume in windows I'd see "this file is corrupt, cant delete it" too.

I ended up presenting new storage for my log volume and restoring from a backup.


Have you checked the health of the log file?

eseutil /ml "C:\LOGS\E00.LOG"

That should tell you the state of the log files. If there is just one that has damaged, you could try repairing it.

Interesting article here:

http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/

Beyond that, deleting log files and such is an option but there are ramifications such as not being able to replay logs. If you have a DAG it might also **** up the replication so I'd remove any DB copies before you do so.

Just my few cents.
 
I checked via eseutil and all was fine. You know why? Because exchange is a retard. That's my conclusion.

I did as i said i was going to do and full backup completed fine. Problem solved!

Will keep an eye out though
 
Rossi... Hey just wanted to touch base with you on the errors that B.E. 2010 were throwing... you stated that you dismounted the D.B., moved files and then remounted the D.B. This resolved the issue for the next backup im assuming that it ran on the 3rd or 4th. Have you run any since and how are they holding up?
 
BackupHelpDJ - do you want for Symantec?

If so, when are you going to fix the complete mess that is Backup Exec 2012?
 
BackupHelpDJ said:
Rossi... Hey just wanted to touch base with you on the errors that B.E. 2010 were throwing... you stated that you dismounted the D.B., moved files and then remounted the D.B. This resolved the issue for the next backup im assuming that it ran on the 3rd or 4th. Have you run any since and how are they holding up?
Click to expand...

Hey there!

Yep, running fine now. Done 2 full backups since, all fine! :)

#Chri5# said:
BackupHelpDJ - do you want for Symantec?

If so, when are you going to fix the complete mess that is Backup Exec 2012?
Click to expand...

Hahaha!!!

I'm sticking with BE2010 until i know BE2012 (or newer) is as good or better.
 
It moved to a single job per server model. So if you had a single job that backed up a number of servers to a single tape (pretty common in my world), you'd end up with one job per server and have to try to chain them to run in sequence. I found instructions to do this via CLI (PowerShell IIRC) but lost the will to live. That's an outstanding progress to move from a GUI (a few clicks for selecting backup targets on each server) to messing around in a CLI.

There's stories on The Reg' of people going from 3 backup jobs to 30+ in 2012. Crazy stuff.

This thread on the Symantec forum covers Symantec putting one-job-multiple-servers back but who knows when it might ship.
 
Last edited:
#Chri5# said:
It moved to a single job per server model. So if you had a single job that backed up a number of servers to a single tape (pretty common in my world), you'd end up with one job per server and have to try to chain them to run in sequence. I found instructions to do this via CLI (PowerShell IIRC) but lost the will to live. That's an outstanding progress to move from a GUI (a few clicks for selecting backup targets on each server) to messing around in a CLI.

There's stories on The Reg' of people going from 3 backup jobs to 30+ in 2012. Crazy stuff.

This thread on the Symantec forum covers Symantec putting one-job-multiple-servers back but who knows when it might ship.
Click to expand...

Indeed!
Did not go down well with a lot of companies. I was warned off of it a while ago, though Insight are still trying to push it on me for my upgrade project next year.
 
Great you are fixed. If this comes up again make sure you dont have aofo enabled on the job. Sometimes that causes this error too.

Have a good one!
 
You must log in or register to reply here.
Back
Top Bottom