[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1608
  • Last Modified:

Backup Exec Job Fails - Corrupt Log Files?

I am running Veritas Backup Exec 10 (w/Exchange Agent), Windows 2003 Server, and Exchange 2000.  I recently started getting the following errors after backup:  

\\SERVER\Microsoft Information Store\First Storage Group Error, Exchange failed to return any log files when backing up \\HINTS10\Microsoft Information Store\First Storage Group

Exceptions
Backup- \\SERVER\Microsoft Information Store\First Storage Group WARNING: "\\HINTS10\Microsoft Information Store\First Storage Group\Log files" is a corrupt file.
This file cannot verify.

Byte counts appear to be normal.  
0
munch007
Asked:
munch007
  • 5
  • 4
1 Solution
 
honmapogCommented:
Are you using the Advanced Open File Option in this job? If so, turn it off.
See also https://forums.symantec.com/syment/board/message?board.id=103&message.id=53239: are you doing a full backup?
0
 
munch007Author Commented:
We are not using Advance Open File Option.  This error occurs when running a Full backup.
0
 
honmapogCommented:
I assume you're not using Circular Logging on the Storage Group either?
Do you see any events in the System or Application event logs at the time of the problem?
Any seemingly unrelated events near the end of the IS backup - when the logs are being backed up?
Are logs being truncated correctly?
Any chance to test backups with NTBackup?
Try putting the IS backup in a job on it's own as a test. Otherwise try changing the order of the resources of your backup job. (Move Exchange backups away from System State or Shadow Copy Components backups).
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
munch007Author Commented:
I assume you're not using Circular Logging on the Storage Group either?

No circular logging

Do you see any events in the System or Application event logs at the time of the problem?

Nothing other than the same error reported in Backup Exec

Any seemingly unrelated events near the end of the IS backup - when the logs are being backed up?

None

Are logs being truncated correctly?

Can you expand a bit on truncating logs?

Try putting the IS backup in a job on it's own as a test. Otherwise try changing the order of the resources of your backup job. (Move Exchange backups away from System State or Shadow Copy Components backups).

This still produces the same error
0
 
munch007Author Commented:
As a test, I ran a backup job of the following on our mail server and was successful:

Local HDD
Microsoft Exchange Mailboxes
Microsoft Public Folder

Not included in the backup:

Shadow Copy Components
Microsoft Information Store
Microsoft SRS
0
 
honmapogCommented:
That last test works because you're not backing up the Exchange Information Store anymore.

With truncating logs I mean that Exchange should remove log files once the Exchange backup has finished. You can check this in the log folder defined for your Storage group. Once the backup is finished, E0xxxxx.log files that you had the day before should no longer be present.
0
 
munch007Author Commented:
At the following location:  C:\Program Files\Exchsrvr\MDBDATA

There is a laundry list of log files, E00104BE, E00104BF, etc.  I read that these shouldn't be removed manually.
0
 
munch007Author Commented:
I ran a full backup selecting only to backup the Microsoft Information Store.  It completed successfully.  The change I made was in the Microsoft Exchange setting of Veritas.  

Exchange server backup method:
WAS - Full - Database & Logs (flush committed logs)
NOW - Copy - Databases & Logs
0
 
honmapogCommented:
The problem with the Copy method is that with this method the logs won't be deleted after each backup and eventually will fill your c:\ drive.
Could you try another full backup of only the infornation store with the original option. Once that backup completes, check if E00104BE and E00104BF are still there - or if they are gone
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now