TimBurlowski
I'm highlighting another improvement that debuts in NetBackup 6.5.2.
You have been able to set priority levels in NetBackup for a long time. The priorities could be set for a policy or for a particular backup or restore job. The higher the priority you assigned to a job the higher it would move in the queue of jobs to run. So if three jobs were all eligible to run at the same time and there was only one tape drive, the job with the highest priority would go first. There are other factors that can play into job priority like how long it has been since the last backup, but you get the idea.
In 6.5.2 you have some new options for job priorities.
First, you can change the default priority for each job type. This means that you can always set the priority for certain jobs like restore for instance to have a higher priority than duplications. 
Secondly, in addition to changing the defaults, you can now change the priority for a running job. Imagine you get to work in the morning and there is a critical job that has been waiting for resources for some time while higher priority jobs have run. If you decide that job must be completed ASAP, you could bump up its priority which would ensure that it will get access to the appropriate resources sooner than it might have otherwise. 
There will be more posts on 6.5.2 to come so stay tuned. Next I plan to help you answer the eternal question, "Why is that job queued anyway?"
