Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Ability to prioritise clients within Policy

Created: 16 Sep 2009 • Updated: 16 Sep 2009 | 7 comments
Andy Welburn's picture
8 Agree
0 Disagree
+8 8 Votes
Login to vote

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.

Comments 7 CommentsJump to latest comment

Andy Welburn's picture

***EDIT of the EDIT** - just realised I could've editted the original, didn't see that View/Edit bit at the top there (was looking at the bottom) :s

I'm sure that said "many, many moons ago" when I first wrote it!! ((Aside: Has someone been editting my content?))

"Many, many months ago" certainly doesn't seem that long ago to be sure (altho' months & moons probably do cover the same approximate period) & I know we weren't running NB4.5 earlier this year. ;)

I could've started it "A long time ago, in a ..."

Well you get the idea - it wasn't recently!

0
Login to vote
David McMullin's picture

On unix, the clients are contained in a file /NB INSTALLPATH/db/class/POLICY/clients

You can alter the sequence there.

BUT - if you add or sort the clients while updating the policy, this gets messed up again.

Adding a field to allow sequence might be a good idea...

NBU 7.0.1 on Solaris 10
writing to EMC 4206 VTL
duplicating to LTO5 in SL8500
using ACSLS 7.3.1

0
Login to vote
Andy Welburn's picture

remember playing with that one (not as) many moons ago, it's just that in 4.5 I remember you could actually sort them in the GUI & it 'stuck'. :)

0
Login to vote
Andy Welburn's picture

I tried editting this file again, just for a laugh, & that's exactly what I did when the jobs kicked off this morning - LAUGH!

I put the client in question at the top of the list & guess where it came in the scheme of things - LAST!

The other clients it decided to do alphabetical today (!) but the REALLY laughable thing is that this client would have come first if all was done alphabetically!!!

0
Login to vote
Marianne's picture

Like with most good ideas, this is the place where they come to die.........

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

0
Login to vote
Andy Welburn's picture

& seems like only a handful with +10 or below ever even got to "In Review".......

0
Login to vote
SymTerry's picture

After quite some time, this has still not changed. All clients within a policy are treated equally as they belong to the same data classification set. What we recommend you to do is to separate the clients into different policies. A new policy can be easily created from an existing policy by 'Copy to new' right click menu. Then adjust the clients as needed and change the priority at the policy level (the priority can be changed at policy attributes pane). Furthermore, you can even adjust the backup start window in the schedules such that higher priority policy gets kicked of by the schedule first. 

Unlike commercial solutions where a 'job' typically represents a container for protected clients; NetBackup uses the term 'job' to represent an instance of the actual running task like backup, restore, duplication, discovery etc. A 'NetBackup Backup Policy' is what represents the container as to what, where, how and when to backup
 
0
Login to vote