Why Backup Exec Fails! 1

[DavidJoshua]

In my case, Backup Exec 8.6 on W2K Server on a Dell PowerEdge 2600.

Backups were failing and I reviewed all of the posts here.

Turned out, based on info on Veritas' site, that if a file is in use, and you don't have the Open Files Option (OFO)(List Price $695, lowest street price that I saw $338), it assumes that the file is corrupt.

It automatically fails the backup and the indication is noted with ^^^^^ at the point of the "corrupt" file.

All of the non-corrupt files are backed up fine.

Solutions?

Buy OFO, or implement the solution at Veritas' website that explains how to make a registry setting change to prevent failure on "corrupt" files.

Now I'm going to look and see what people here think about OFO.

Hope this saves you some time!

-=david=-

 

[cybersaur]

DJ,

I'm not a big fan of editting the registry to avoid some red letters in the activity log. its good that you've restored the data to ensure it is being backed up, but imagine a scenario where it really did fail and wasn't properly reported because of the registry change.
You're backing up financial data. You need to ask yourself if backing up this data properly is worth more than $338 - $695.
I'd say get the OFO and sleep easier at night.

Trent
Network Admin

 

[DavidJoshua]

Yes. I agree. I was hoping to save someone the time I spent figuring out why open files >> corrupt files >> failed backup.

-=david=-