cancel
Showing results for 
Search instead for 
Did you mean: 

Help: Netbackup 6MP4 Job priority

Robert_H_Abed
Level 4

Hi,

I am facing the following problem on Netbackup 6 MP4. I have created 2 Windows policy: Customer_Windows_1 and Customer_Windows_2. The Job priority on Customer_Windows_1 is 10 and the Job Priority on Customer_Windows_2 is 5. I have set the same schedules for both policies:

Cumulative: everyday but Friday from 12:00AM to 5:00AM
Full: every Friday from 12:00AM to 12:00PM (every Friday except first Friday of the month)
Full_Monthly: every First Friday of the Month.

Customer _Windows_1 policy contains around 20 clients and Customer_Windows_2 contains only 1 client.

The backup is done on the same volume pool.

Since the schedules are set at the same time, the jobs order depends on the Job Priority. So backup of the clients in Customer_Windows_1 should start before the client of the Customer_Windows_2.

In my case, this is not happening; the backup job of the client of customer_Windows_2 is starting before the backup jobs of the Customer_Windows_1.

How can I resolve this issue? I need the backup job of the policy with highest job priority to start before the backup job of the policy with the lowest job priority.


Thanks
Robert
10 REPLIES 10

Rakesh_Khandelw
Level 6
Are you seeing same behaviour on all of the three schedules you have mentioned or is it on one particular schedule?
 
post bppllist commad output for these two policies
 
bppllist Customer_Windows_1 -U
 
bppllist Customer_Windows_2 -U

Robert_H_Abed
Level 4
Hello,

Since I implemented the 2nd policy, only one weekly full backup has passed. The job with smaller priority was performed after the jobs with higher priority. I am currently facing the problem on the incremental backups.
I can wait for this Week End backup and let you know if I face the problem on the Full.

Please note that the 2 policies are exactly the same. I created 2 policies since I was not able to set the priority on the clients by editing the C:\Program Files\VERITAS\NetBackup\db\class\Customer_Policy\clients file.

Below is the output requested:
Policy Name:       Customer_Windows

 Policy Type:         MS-Windows-NT
 Active:              yes
 Effective date:      06/20/2005 18:11:23
 Backup network drvs: no
 Collect TIR info:    no
 Mult. Data Streams:  no
 Client Encrypt:      no
 Checkpoint:          no
 Policy Priority:     10
 Max Jobs/Policy:     Unlimited
 Disaster Recovery:   0
 Collect BMR info:    no
 Residence:           ddci-bk1-hcart2-robot-tld-1
 Volume Pool:         Solaris-Linux
 Keyword:             (none specified)

 HW/OS/Client:  PC            WindowsNET    delsrv16-bk.qidc.bak
                PC            WindowsNET    delsrv14-bk.qidc.bak
                PC            WindowsNET    dellisa1-bk.qidc.bak
                PC            WindowsNET    dellisa2-bk.qidc.bak
                PC            WindowsNET    dellsrv3-bk.qidc.bak
                PC            WindowsNET    dellsrv4-bk.qidc.bak
                PC            WindowsNET    dellsrv5-bk.qidc.bak
                PC            WindowsNET    dellsrv6-bk.qidc.bak
                PC            WindowsNET    dellsrv7-bk.qidc.bak
                PC            WindowsNET    dellsrv8-bk.qidc.bak
                PC            WindowsNET    dellsrv9-bk.qidc.bak
                PC            WindowsNET    delsrv10-bk.qidc.bak
                PC            WindowsNET    delsrv11-bk.qidc.bak
                PC            WindowsNET    delsrv12-bk.qidc.bak
                PC            WindowsNET    delsrv13-bk.qidc.bak
                PC            WindowsNET    delsrv15-bk.qidc.bak
                PC            WindowsNET    ddcc-hpsrv2.qidc.bak
                PC            WindowsNET    ddcc-hpsrv3.qidc.bak
                PC-IA64       WindowsNET    ddcc-hpsrv4.qidc.bak
                PC            WindowsNET    hpsrv1-bk.qidc.bak
                PC            WindowsNET    ddcc-hpsrv1.qidc.bak

 Include:  ALL_LOCAL_DRIVES

 Schedule:          Full_Monthly
   Type:            Full Backup




C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist.exe Customer_Windows_Po
licy -U
------------------------------------------------------------

Policy Name:       Customer_Windows_Policy

 Policy Type:         MS-Windows-NT
 Active:              yes
 Effective date:      05/06/2007 08:57:15
 Backup network drvs: no
 Collect TIR info:    no
 Mult. Data Streams:  no
 Client Encrypt:      no
 Checkpoint:          no
 Policy Priority:     5
 Max Jobs/Policy:     Unlimited
 Disaster Recovery:   0
 Collect BMR info:    no
 Residence:           (specific storage unit not required)
 Volume Pool:         Solaris-Linux
 Keyword:             (none specified)

 HW/OS/Client:  PC            WindowsNET    ddci-wtr1-c.qidc.bak

 Include:  ALL_LOCAL_DRIVES

 Schedule:          Full_Monthly
   Type:            Full Backup

Please note the client names are just informational

Thanks
Robert

Clayton_Walter
Level 4
Maybe this will help...
 
If Policy 1 has a priority of 10 and Policy 2 has a priority of 5 then Policy 1 will always get queued first UNLESS any of the clients in Policy 2 did not complete successfully the last time they ran.  NetBackup will queue up the clients that haven't been backed up successfully first and then it will adhere to the policy priority.  
 
If your backups aren't completing on time consistently, you probably need to re-evaluate your backup windows and/or data that you are backing up for starters.
 
Cheers!
 
Clayton 

Message Edited by Clayton Walter on 05-15-200701:00 PM

Robert_H_Abed
Level 4
Hello Clayton,

Thanks for the reply.
Even if the client backup is successful, the next backup is not being done as per the priority.

I did not understand why I should re-evaluate the data and the backup window?
I am backing up ALL_LOCAL_DRIVES, and the backup window is the same for both priority. I could set the backup window on Policy 2 to start 5 or 10mn after the backup Window of Policy 1, but this is only a workaround.

My only concern is how to priotize the clients since setting the priority for all clients using the C:\Program Files\VERITAS\NetBackup\db\class\Customer_Policy\clients as in  NBU5.1does not work.
I suppose that this is because of:
"The order of the jobs on the worklist is dynamic, taking into account many factors. The following items are examples of factors that could effect the order of jobs on the worklist:" (from the Admin 2 Guide).


Cheers,
Robert

Clayton_Walter
Level 4
Robert,
 
I mentioned re-evaluating your backup schedules and data being backed up because you mentioned in an earlier post that some of the backups weren't completing on time. That was just a suggestion...
 
You mentioned that you manually changed the priority in C:\Program Files\VERITAS\NetBackup\db\class\Customer_Policy\clients.  I'm running 6.0MP4 and as far as I can tell the priority is set in the info file under that same path.  Check this file if you haven't already and verify that the correct priority is set there.
 
The info file should look something like this:
 
CLIENT_TYPE 13
FOLLOW_NFS_MOUNTS 0
CROSS_MOUNT_POINTS 1
CLIENT_COMPRESS 0
PRIORITY 1
CLIENT_ENCRYPT 1
DISASTER_RECOVERY 0
MAX_JOBS_PER_CLASS 2147483647
MAX_FRAG_SIZE 0
ACTIVE 0
EFFECTIVE_TIME 1136349173
COLLECT_TIR_INFO 0
EXTENDED_SECURITY_INFO 0
IND_FILE_RESTORE_FROM_RAW 0
BLOCK_INCREMENTAL 0
STREAMING 0
FROZEN_IMAGE 0
BACKUP_COPY 0
NUMBER_OF_COPIES 1
FAIL_ON_ERROR 0
CHECKPOINT 0
CHKPT_INTERVAL 0
ENABLE_PFI 0
OFFHOST_BACKUP 0
USE_ALT_CLIENT 0
USE_DATA_MOVER 0
DATA_MOVER_TYPE 2
COLLECT_BMR_INFO 0
CLASS_ID 965C6CE7650A4DF7934ACF4AAB347687
RESIDENCE *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
POOL NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup
#VMD5_DIGEST=1b 4d 9a fe 94 cb c3 8a f3 34 13 4a d6 71 73 84
 
I'm also curious what's preventing you from changing the policy priority using the change policy option in the NB admin console? 
 
Clayton

Message Edited by Clayton Walter on 05-16-200706:34 AM

Robert_H_Abed
Level 4
Hello Clayton,
Maybe I was not clear enough with my explanation:

I am not changing the priority of the policy in the info file. I am doing so in the Admin Console.

My first plan actually was to have 1 and only 1 policy for my customers.
In Netbackup 5, I had the option to start the backup of a client before another by editing "clients" file in C:\Program Files\VERITAS\NetBackup\db\class\Customer_Policy\ . In Netbackup 6, even if I edit the file, this won't help. This is why I created a new policy with a higher priority, in order to start a client in the new policy before the client in the old policy.

By only changing the Job Priority field, so far, the order of the backups between the 2 policies is not as requested. The Jobs in the higher priority policy dont always start before the jobs in the lowest priority policy.

A workaround is to start the schedule of the policy with lower priority after the one with the higher prioirty.
I am trying to figure out why the job priority field is not actually setting the jobs priority as per the policy; or maybe I missed some configuration / settings?

Thanks
Robert

Chad_Wansing_2
Level 3
Personally, for something like this, I'd give the lower priority job a 10-minute offset to let the other job kick off first.  Once it's running, there's no way the lower priority job should grab a drive from it.  If it does, then you know there's something funny going on.  When you schedule things at exactly the same time, I've seen some strange stuff happen.

Rakesh_Khandelw
Level 6
Hi Robert,
 
I was interested in seeing settings for your schedules in your policices but for some reason the policy information you had posted does not have it. May be windows does not use -U option (it works for me in UNIX environment). Can you post schedule settings for both of the policies? One thing I suspect, your schedules are probably frequency based and that is why it's not working the way you want it to. Look into schedule settings.

Robert_H_Abed
Level 4
Hello Rakesh,
thanks for your reply and your assistance. Sorry for the late reply since I was busy with criticial problems here.
Please find below the details of the schdules (I issued the following: bpplsched Customer_Windows -L)

Customer_Windows
-----------------
Schedule:          Full_Monthly
 Type:            FULL (0)
 Calendar sched: Enabled
   Friday, Week 1
 Retention Level: 5 (3 months)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     Full_Monthly_All
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  000:00:00
  Monday      000:00:00  000:00:00
  Tuesday     000:00:00  000:00:00
  Wednesday   000:00:00  000:00:00
  Thursday    000:00:00  000:00:00
  Friday      000:00:00  012:00:00   120:00:00  132:00:00 
  Saturday    000:00:00  000:00:00

Schedule:          Full
 Type:            FULL (0)
 Calendar sched: Enabled
   Friday, Week 2
   Friday, Week 3
   Friday, Week 4
   Friday, Week 5
   EXCLUDE DATE 0 - 03/09/2007
 Retention Level: 3 (1 month)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     (same as policy volume pool)
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  000:00:00
  Monday      000:00:00  000:00:00
  Tuesday     000:00:00  000:00:00
  Wednesday   000:00:00  000:00:00
  Thursday    000:00:00  000:00:00
  Friday      000:00:00  012:00:00   120:00:00  132:00:00 
  Saturday    000:00:00  000:00:00

Schedule:          Cumulative-Inc
 Type:            CINC (4)
 Frequency:       1 day(s) (86400 seconds)
 Retention Level: 3 (1 month)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     (same as policy volume pool)
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  005:00:00   000:00:00  005:00:00 
  Monday      000:00:00  005:00:00   024:00:00  029:00:00 
  Tuesday     000:00:00  005:00:00   048:00:00  053:00:00 
  Wednesday   000:00:00  005:00:00   072:00:00  077:00:00 
  Thursday    000:00:00  005:00:00   096:00:00  101:00:00 
  Friday      000:00:00  000:00:00
  Saturday    000:00:00  005:00:00   144:00:00  149:00:00 


Customer_Windows_Policy
------------------------
Schedule:          Full_Monthly
 Type:            FULL (0)
 Calendar sched: Enabled
   Friday, Week 1
 Retention Level: 5 (3 months)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     Full_Monthly_All
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  000:00:00
  Monday      000:00:00  000:00:00
  Tuesday     000:00:00  000:00:00
  Wednesday   000:00:00  000:00:00
  Thursday    000:00:00  000:00:00
  Friday      000:00:00  012:00:00   120:00:00  132:00:00 
  Saturday    000:00:00  000:00:00

Schedule:          Full
 Type:            FULL (0)
 Calendar sched: Enabled
   Friday, Week 2
   Friday, Week 3
   Friday, Week 4
   Friday, Week 5
 Retention Level: 3 (1 month)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     (same as policy volume pool)
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  000:00:00
  Monday      000:00:00  000:00:00
  Tuesday     000:00:00  000:00:00
  Wednesday   000:00:00  000:00:00
  Thursday    000:00:00  000:00:00
  Friday      000:00:00  012:00:00   120:00:00  132:00:00 
  Saturday    000:00:00  000:00:00

Schedule:          Cumulative-Inc
 Type:            CINC (4)
 Frequency:       1 day(s) (86400 seconds)
 Retention Level: 3 (1 month)
 u-wind/o/d:      0 0
 Incr Type:       DELTA (0)
 Alt Read Host:   (none defined)
 Max Frag Size:   0 MB
 Synthetic:       0
 PFI Recovery:    0
 Maximum MPX:     1
 Number Copies:   1
 Fail on Error:   0
 Residence:       (specific storage unit not required)
 Volume Pool:     (same as policy volume pool)
 Daily Windows:
  Day         Open       Close       W-Open     W-Close
  Sunday      000:00:00  005:00:00   000:00:00  005:00:00 
  Monday      000:00:00  005:00:00   024:00:00  029:00:00 
  Tuesday     000:00:00  005:00:00   048:00:00  053:00:00 
  Wednesday   000:00:00  005:00:00   072:00:00  077:00:00 
  Thursday    000:00:00  005:00:00   096:00:00  101:00:00 
  Friday      000:00:00  000:00:00
  Saturday    000:00:00  005:00:00   144:00:00  149:00:00 

Can you please let me know why the frequency based schedule wont work?

Regards,
Robert

Rakesh_Khandelw
Level 6
You are not seeing the desired behaviour on your incremental backups possibly because  schedule is frequency based.
 
Frequency specifies how much time must elapse between successful automatic backups for clients on this schedule type within a single Policy.
 
You may want to try lowering the frequency on high priority job so that it meets the criteria before windows open, that way job gets higher in worklist.