FYI..... below is the actual way bpduplicate runs with the id switch. This could
mean tape request contention (oh well). I guess if you used different tape pools
for different classes you could get around the issue somewhat.


Netbackup support response below:

Here's what I've found regarding the bpduplicate syntax (from a ticket
dealing with the same issue in our UNIX documentation):

This is a documentation issue

Instead of:

"If the original is
fragmented between different media IDs, NetBackup duplicates only the
fragments that exist on the specified media ID."

the doc (Sys admin guide and man pages) should say something like:

"If the original is fragmented between different media IDs, NetBackup
duplicates only the backups that exist on the specified media ID.  The
backup that spans media will be duplicated, but not any other backups
on the spanned media ID."


So, the short of it is that you aren't going crazy and the documentation IS
incorrect.  When you kicked off a bpduplicate with the -id option, it is
normal that it should ask you to mount the media that contains the first
fragment of the image(s) on the media ID that you specified.