Backupexec 12.5 Corrupt Items

[StevenHill]

I have Backup Exec 12.5 installed and I keep having my backup jobs fail on open PST files. The OFM agent is installed on the server I back up. I may be missing something here, but how can I stop Backup EXEC reporting this as a failure?

Job ended: December 28, 2010 at 5:11:39 AM
Completed status: Failed
Final error: 0xe000fe36 - Corrupt data encountered. See the job log for details.
Final error category: Resource Errors
 

Execptions Area

Backup- \\MYServer\G:
WARNING: "\\MYServer\G:\Users\Travel\Travel.pst" is a corrupt file.
This file cannot verify.
Backup- \\MYServer\D:
The .DR file that is required for Intelligent Disaster Recovery is not updated.
 

[ZeRoC00L]

Have found this for you:

HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec for Windows\Backup Exec\Engine\Backup

On the menu bar, select Edit | Add Value

In the Value name field, type in Fail Jobs On Corrupt Files

For the Data Type, select REG_DWORD

In the right window, double-click Fail Jobs on Corrupt Files

Leave the value at its default (zero - 0)

Restart the Backup Exec services or reboot the Windows server.

BE will then report that the Backup was successful on the next backup, with exceptions (it'll say the PST is corrupt but won't fail the entire job due to an open PST).  

[AmolB · Accepted solution]

Hello

 Try the above steps else use AOFO. Refer to the below link.

 http://www.symantec.com/docs/TECH145966

[StevenHill]

I see that AOFO was not enabled on the job, I have marked this now and will check it out. I may try the Corrupt registry key also. Do you know if that is set on the server or the client?

[ZeRoC00L]

You need to set it on the server.

[Ken_Putnam]

If you do try the Registry tweak, be aware that ANY corrupt file message will be bypassed, not just open PST files

[CraigV]

...I wouldn't go around suggesting this as a fix for an issue unless you want a seriously angry forumite who goes off about hating Symantec again when they need to restore something and cannot.

It should be a TEMPORARY step in the troubleshooting process, nothing more.