I wager you are running Netbackup 5.1MP4...

We just ran into this at my workplace.  This "feature" was introduced in MP4.

Here is what to do:

echo 1 > /usr/openv/netbackup/MAX_STAGING_JOBS

Take a look at this technote (now missing from veritas' site) if you
need to clean up your dssu due to the 191's:

http://72.14.207.104/search?q=cache:Ieb2QUFwcn0J:seer.support.veritas.com/docs/267636.htm+manually+clean+dssu+veritas&hl=en&lr=&client=firefox-a&strip=1

Hope it helps.

-Shane

On 5/5/06, Brooks, Jason <brooksje AT longwood DOT edu> wrote:
> I've been noticing that I'm frequently, if not daily, receive a 191 on a
> duplication job.  So, today, I dug a bit deeper.  Here's what happens:
>
> The parent scheduled relocation job kicks off and spawns the first
> relocation job.  At some point during that job's running, a second one
> kicks off and ends with a 191:
>
>
> 5/5/2006 2:14:05 PM - Error bpduplicate(pid=10876) Duplicate of backup
> id Readpac_1146810660 failed, file write failed (14).
> 5/5/2006 2:14:05 PM - Error bpduplicate(pid=10876) Status = no images
> were successfully processed.
> 5/5/2006 2:14:06 PM - end Duplicate; elapsed time: 00:01:53
> no images were successfully processed(191)
> 5/5/2006 2:14:06 PM - Error bptm(pid=2976) unable to read bpduplicate
> message, network read error (h_errno = 10054)
>
> When looking at the details of the first running relocation job, I found
> that the image, Readpac_1146810660, was already relocated by the first
> job once the second tries to grab it.
>
> Does NBU not keep track of the fragments on relocation?  Is there some
> config, related to multiple jobs, that should be changed?
>
> Thanks,
> Jason
>
>
> ------------
> Jason Brooks
> Computer Systems Engineer
> IITS - Longwood University
> voice - (434) 395-2916
> fax - (434) 395-2035
> mailto:<brooksje AT longwood DOT edu>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>