Event Notications, Log Files, Error Handling - Got any clues?

[kingservant]

My company uses Veritas BE to backup critical medical data. We have encountered instances where the tape backup hardware has failed for some reason or another. I would like to know, aside from email notication, SNMP, etc., if there is a way to trap fail events sent by BE so that our software can pick up the fault message. If BE creates a log file with the error notification inside that would help. If BE sends a windows message that can be picked up from other software outside of their service, that would help too.

 

[dvannoy]

inside the BackupExec directory there should be a folder called LOG. inside there you will have the server log and a few more.

Veritas also has files that are created when running a diag that have the file extension of FAX..

you can also put BackupExec in a debug mode by pressing Crtl+z then it will write results to a file..

what version are you running?? what OS

 

[kingservant]

Oh, thank you. I almost gave up hope on getting a reply. The version that i'm running is 8.6 under Win2K. I looked for the subdirectory that you stated but I don't see a LOG directory. All of the log file on my machine are being backed up in the Data directory, is that the same thing? Also, when I do the ctrl_z thing, what is the name of the file and what directory does it reside.

 

[CadAtIbex]

Hi, kingservant, from Edinburgh, Scotland.

On BEX 8.6 here, click Tools, Notification Setup..., SNMP tab. Make sure Send Backup Exec Traps is selected, then click Help for an extremely helpful and detailed all-you-never-wanted-to-know-about BEX SNMP Traps.

I hope this helps? ...this is my first post here!

Now hopefully, I can figure out how to stop BEX being unable to create BeTopCat.Idx because we use secured Jet/DAO databases here and BEX barfs on that, hence no catalogs get written 8-{ ...anyway, I'm off to check the other threads as I feel this MUST be an FAQ: if not, I'll be polite and start a new thread rather than 'hi-jack' this one! ;-)