|
|
Question : Backup Exec Crashing Jobs
|
|
Hi,
My problem is that Backup Exec appears to crash big jobs either to my tape library or to disk. I can do a manual backup without problems and watch it via terminal services. If I then close TS (disconnect or log off) and look again the next morning this job has crashed. The errors from the Tape library say the job has been cancelled by user recovery and that the tape hardware is offline. The backup to disk shows the job as failed. Both of these have a corrupt backup log. I read a few articles implying it might be network problems but so far haven't seen any. I created a hosts file for resolution just in case. I have a couple of errors in the event logs on the server -When the crash happens: The Backup Exec Job Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. -and this one The redirector was unable to initialize security context or query context attributes. Plus the standard ones that get logged that the job didn't complete.
Kit: -DL380 G1 with Windows 2000 server -SSL1016 Autoloader Ultrium460 Drive -Gigabit nic's and switch
Things I have tried: -Changing scsi drivers -Updating BE10 and Windows with all current patches -reloading the backup server -defragging all servers involved -checking all firmware (scsi, tape library). -creating a hosts file with all relevant servers -replacing the drive in the ssl1016 (before I realised it happened on Backup to Disk as well) -adding more ram to the server -checking the Compaq tools for the server - all ok apparently.
thanks for any help
Andy
|
Answer : Backup Exec Crashing Jobs
|
|
Heya Andy
Couple of things that come to mind:
What time does it happen? It may be conflicting with your Exchange maintenance:
http://seer.support.veritas.com/docs/241858.htm
Also, have you turned on debugging to see if you can get any more info? Stop all the BE services, and for the Backup Exec Engine service, go into the properties before restarting it, and enter "-debug" in the startup parameters field. This will turn on extended logging in your c:\Program Files\Veritas\Backup Exec\NT\Logs (off the top of my head) folder, which may give you some more indication why this is happening.
Also, you may just want to confirm that the Backup Exec Remote Agent is installed on the remote machine. That's something I've screwed up in the past :)
|
|
|
|
|