How can I solve Backup Exec full backup issue caused by exchange transaction log?

Gordon Tin
Gordon Tin used Ask the Experts™
on
Background:
Backup Exec version 20.0 1188.1863
Exchange2010

Issues
Full Backup file Fail w/ the following messages:
---------------------------------------------------------
 The consistency check of the snapshot for the Microsoft Exchange database Database was successful.
Monday, May 20, 2019 9:37:17 AM - V-79-57344-65247 - A failure occurred reading an object.

Monday, May 20, 2019 9:37:18 AM - WARNING: "\\concor-ex.XXXdomain.net\Microsoft Information Store\Mailbox Database 1\Database" is a corrupt file. This file cannot verify.
The consistency check of the snapshot for the Microsoft Exchange transaction log Logs ( E0000803337.log - E00008037B8.log ) has failed.  You should check for possible data corruption in the transaction log that is online.
-------------------------------------------------------

The Exchange seems running ok but can't backup

What is the issue with the exchange transaction log?
How can I solve it?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Iamthecreator OMIT/EE Solution Guide
Commented:
Is this a GRT based backup?
Run a non-GRT backup without the option of performing a consistency check. This will flush the logs.
Once the backup completes, enable the GRT option and run as usual.
Top Expert 2014
Commented:
Another option is to dump the transaction log by turning on circular logging for an hour or so, then turn it off again.
As Andyalder said enabled and disable the circular logging i would suggest to avoid any future restore of this backup
AmitIT Architect
Distinguished Expert 2017

Commented:
Go with option suggested by @Iamthecreator OM. I have done similar with Microsoft DPM long back.
Top Expert 2014

Commented:
Mine was just an alternate method of flushing the logs .Restores will be a bit dodgy after that of course but the toilet will still function.
Gordon TinIT Manager

Author

Commented:
Dear All

I following suggest from "Iamthecreator OM".
i Ran a non-GRT backup without the option of performing a consistency check.

Result: Completed status: Failed
(The logs is not seems to be flushed! it is still there).


Wednesday, May 22, 2019 9:52:47 AM - V-79-57344-65247 - A failure occurred reading an object.
Wednesday, May 22, 2019 9:52:47 AM - WARNING: "\\concor-ex.xxxdomain.net\Microsoft Information Store\Mailbox Database 1\Database" is a corrupt file. This file cannot verify.


--------------------------------------------------
I have the following question:
1.  How can I fix the corrupted file?
2.  Am I correct that the issues are both 1. DB and 2. logs?  (AS the Db is currently running ok)
Top Expert 2014

Commented:
If the DB is corrupt you have to run eseutil and isinteg against it same as when Exchange first came out.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial