From the man page for bpconfig:
The number of retries
for a backup, during the configured time period (see -period).
NetBackup tries to run a backup job for a given client/policy/schedule
combination the specified number of times in the configured period. This option
lets you to limit the number of backup attempts if repeated failures occur.
Note: This attribute does not apply to user-directed backups and archives.
So a manual backup will not retry, but you can
config for jobs kicked off by a policy to retry as many times as you want –
within the open window. Default is twice.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Nathan
Kippen
Sent: Wednesday, December 16, 2009 7:56 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Q: Job retry attemps with multiplexed jobs
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?
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
