Sheduled Jobs failures

[Brian_Small_2]

Hi All,

I retired a Compaq server and moved the Benchmark DLT tape unit to a new, W2k server using a new SCSI controller (LSI Ultra 320 2000 series), and did a fresh install of Backup Exec 9.

The backups had been running flawlessly in the old server.

Now, most jobs which I manually submit (Run Now) work just fine, but when I schedule the same job, it fails when it runs, even when using the same tape.

In fact, I've only had one manually submitted job fail, and when it did, it was the same failure as the scheduled job failures.

So I can for now comfortably get backups with a little work on my part.

When the job fails, it always fails at the same point: I always get the same amount of data within a few k, and the job runs for the same amount of time, within a few seconds / less than a minute difference.

In the Event logs, I get this error starting after the job has run for about 7 minutes, then the job errors out and quits about 19 minutes after it started.
Here's the error:

Category: None
Event ID: 7
Description: The device, \Device\Tape0, has a bad block.



This error is patently not true. The same job, the same data, the same tape perform flawlessly most times when I submit the job manally. And, I have changed all the old tapes for new ones. This is very consistent, I've had over 2 weeks of failures and about 5 manually submitted successes.


In the Job Log I get this information:

Job ended: Tuesday, May 02, 2006 at 11:19:40 PM
Completed status: Failed
Final error code: a00084f9 HEX
Final error description: A communications failure has occurred between the Backup Exec job engine and the remote agent.

Final error category: Resource Errors
Error rule Resource Errors was applied.
Job was not scheduled for retry because out of retries.
Final disposition: Job scheduled for next occurrence.


A Google search for this error yield information (on this Symantec site) about resetting the Network Adapter used to backup remote agents.

I have made the changes suggested with no improvement.

However, I am not backing up any remote agents. I'm only backing up 2 directories on the local server

Any ideas?

[Russ_Perry]

The event 7s can mean a lot of different things. Compare the data you're getting in the events to http://support.veritas.com/docs/241684 to see more specifically what the cause is.

Russ

[Brian_Small_2]

Thank you for your info, unfortunately I don't know how to make use of it.

According to the link you gave me the codes in the error indicate a "Medium Error"
/ "Position error detected by read of medium"

While this might be true, I need to know what could be causing it. In other words, the Position error (which I didn't know to read until you pointed me there) doesn't bring up an idea of where to go from here.

And, the Position Error being generated in the event log doesn't make sense, as the same tape in the same drive consistently works when I submit the job to "Run Now" but not when I schedule it and let it run from the schedule. Furthermore, I get just over a gigabyte of backup before it fails each time.

Also, the error in the backup log is hugely different, indicating a communications failure with a remote agent rather than a position error on the medium.

Which is odd because I'm not backing any remote agents, the tape unit is local to the server I'm backing up, and that's all I'm backing up.

[tejashree_Bhate]

Hello,

As a preliminary step please upgrade to version 9.1 Backup Exec and also update all remote agents.


<<>>

<<>>

<<>>

<<>>

<<>>

Check that the remote agent service is running under local system account on the media as well as the remote server.


Note:- if we do not receive your reply within two business days, this post would be assumed answered and archived.