CLIENT SORTED IN POLICY
Many, many months ago (probably NB4.5, maybe even NB5.1?), the sequence in which clients were 'input' in the Policy determined the order in which the jobs ran i.e. the client at the top of the list ran first, followed by the second and so on.
Now, the list of clients gets sorted alphabetically & (I believe) the sequence is determined by the success of the previous 'run' i.e. if a client failed in the previous run for whatever reason then that client runs first next time out in order to allow for a successful backup (or something along those lines!) which in itself is no bad thing.
We have a Policy (well many really!) with a number of clients, say 8, & a max jobs per policy set to, say, 4. One of these clients takes most of the working day to backup - even if it starts first all the others will finish before it does. In NB6.5.4 (& maybe before?) you can change the priority of the jobs once they are queued or running, so I try & catch this particular client (which is invariably queued) & change its priority so it starts as soon as possible.
I think it would be a good idea to allow for this type of prioritisation actually within the Policy itself (maybe even to backup selection level?) to allow admins to more finely tune their backup environment.
Just a small query..
Which one is valid in NBU 7,.1 OUT OF THE 2 LINKS?