Jobs crash server HARD

[Andrew_Wasson]

BE 10 on Server 2000 (SP4 pre-rollup) backs up other servers in the environment with no issue until it tries to back itself up.

After a couple of seconds or up to 7 minutes, the job runs until the server just stops. No crash screen, no log entry, no notification. The server just stops responding to the OS GUI, then after a couple of seconds, stops responding to pings.

It is running eTrust as its antivirus product but otherwise it is just a file and print server.

BE 10 is patched up to build 5520 and the Website diags give it a passing eval.

I am stumped since there is absolutely no error messages to check out.

The OS is a recent install with updated hardware drivers for the SCSI cards and Veritas drivers for the tape hardware, Dell PE 1300 server.

Any suggestions would be appreciated.

[Amruta_Purandar]

Hello,

- Please create a separate job just for the Media server
- Check if there are any alerts
- Does it give any errors?
- Please start the following debug utility and send us te relevant part of the log.
Title:
How to use the SGMON utility to perform a live debug of Backup Exec
http://support.veritas.com/docs/190979


Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Andrew_Wasson]

There are no error messages in any log I can located.

The status of the job that fails comes up as failed and is reported as no bytes backed up. Wndows event viewer has nothing in either the System or Application logs except restart messages.

This is a production server so causing it to crash during the business day is difficult to get permission to do.

The other steps you suggest have already been done with the server jobs set up individually instead of in one big job.

[Shyam_Sundar]

Hello,

Also check what the drwtsn32 log says. Activate the drwtsn32 logging before the server crash so that we can arrive close to finding the root cause of the issue.


Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Thanks.