maybe i've got this wrong, but it always seemed to me that when netbackup started a sql policy in Netbackup 5.1, the parent job would stay as queued until there was a drive available for it to use. yet with Netbackup 6.5, what we are finding is that the parent jobs all go active, and then we end up with thousands of child jobs sitting there queued until a tape drive is free.
and to make matters worst, they all seemed to let filesystem backups take precedence, as if the sqkl backup priority was a minus value!

please tell me i'm imagining this and that i'll wake up and everything will be ok!

cheers