Hi,
  Here's my problem, a backup job writes to a media and then fails
with write error/position error etc. The job then gets re-queued and
runs again, then NBU uses this very same tape and writes and fails
again, this happens till the max retires of the job is exceeded and
then the job fails.
Why does it reuse the same tape again and again for the same
job/policy? Is there a counter that we can set to prevent NBU from
retrying a media that errors out the first time?
The logs below from bptm show the media ID 001956 being repeatedly used.

02:01:58.703 [5842] <2> log_media_error: successfully wrote to error
file - 10/27/05 02:01:58 001956 13 POSITION_ERROR
02:29:33.454 [21029] <2> log_media_error: successfully wrote to error
file - 10/27/05 02:29:33 001956 13 POSITION_ERROR
03:19:20.128 [22766] <2> log_media_error: successfully wrote to error
file - 10/27/05 03:19:20 001956 13 POSITION_ERROR
04:30:34.394 [25958] <2> log_media_error: successfully wrote to error
file - 10/27/05 04:30:34 001956 13 POSITION_ERROR

  Ironically, the 5th time it successfully wrote to this tape and
continued with the job.
We run huge NDMP jobs (average size of each is 2 TB) so when this
happens say 70% into a job, NBU has to start from the beginning, sadly
checkpoint restart is not an option for NDMP backups. Is this
available in 6.0?


-G