Hi,

'kicked off manually'

AFAIK manually kicked backup jobs off jobs will _not_ retry, same applies 
for Oracle backups, you need to handle this on the host you are backing up 
from, e.g., check if it was successful or not and retry if not.

Justin.

On Wed, 16 Dec 2009, Nathan Kippen wrote:

> I have a job that is kicked off manually every day .. (I have Tivoli
> monitoring this particular backup.)
>
> I have 36 streams writing to 18 tape drives.  Every now and then I get a
> media error (status 84) on a drive which causes two streams to fail (since
> they are multiplexed).  The tape drive is automatically cleaned; however,
> netbackup does not attempt to restart the job.  These errors always occur
> outside of business hours and so when I come in, the job is always in a
> 'failed' status and I have to restart from the beginning.
>
> Do jobs not try to restart when they get a status 84?
>
> bpconfig -U
>
> Job Retry Delay:              6 minutes
> Max Simultaneous Jobs/Client: 100
> Backup Tries:                 3 time(s) in 12 hour(s)
> Keep Error/Debug Logs:        15 days
> Max drives this master:       0
> Keep TrueImageRecovery Info:  9 days
> Compress Image DB Files:      older than 90 day(s)
> Media Mount Timeout:          60 minutes
> Shared Media Mount Timeout:0 minutes (unlimited)
> Display Reports:              24 hours ago
> Preprocess Interval:          4 hours (default)
> Maximum Backup Copies:        4
> Image DB Cleanup Interval:    12 hours
> Image DB Cleanup Wait Time:   60 minutes
> Policy Update Interval:       10 minutes
>
> Thanks
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu