NetBackup - All jobs don't queue

[KDOG1122]

I created a backup policy that has 90 clients that run Full backups on Fri. 6pm - Mon. 6am. I have a LOT3 tape library with four drives.  When the backup job kicks off on Friday 6pm it will start backing up four clients and only queue 26 clients out of the 90 clients.  The same thing will happen on Saturday and Sunday, meaning it will start backing up the next 30 clients and Sunday at 6pm it will start the last 30 clients.  I'm not running separate policies.  I configured one policy but it's breaking the job up into three separate stages.  I created a new backup policy to see if it would happen again and it works for one day and goes back doing the same thing over again.  But here's the kicker, I have a Incremental backup in that same backup policy with the same amount of clients and that works just fine. Since the jobs don't run consecutively the jobs run into production time which slows our network down. Can you please provide some assistance?

Thanks!

[ahlip]

Version, patch level?

Run the command "bppllist -L <policy_name>" and let us see the output here

[KDOG1122]

C:\>bppllist HQ_Windows_Server -L

Policy Name:       HQ_Windows_Server
Options:           0x0
template:          FALSE
c_unused1:         ?
Names:             (none)
Policy Type:       MS-Windows-NT (13)
Active:            yes
Effective date:    12/21/2007 00:29:27
Client Compress:   no
Follow NFS Mnts:   no
Backup netwrk drvs:no
Collect TIR info:      no
Mult. Data Stream: no
Perform Snapshot Backup:   no
Snapshot Method:           (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup:    no
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           2
Use Alternate Client:      no
Alternate Client Name:     (none)
Use Virtual Machine:      no
Enable Instant Recovery:   no
Policy Priority:   0
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         GPO_Storage_Group
Volume Pool:       Diff_Tape_Pool
Server Group:      *ANY*
Granular Restore Info:  no
Client/HW/OS/Pri:  bianca PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  budgetapps PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  ciscolms PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  Ciscosecure PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  Ciscovms PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  cordelia PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  covelite PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  cs-files PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  csbdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  docs-sales-svr1 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  docs_ordersbdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  docs_orderspdc PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  docs_salesbdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  eidspc203 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  epassportad02 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  fluorite PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  fmsapps PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  fmsbudps2 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  fmsnfc01 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  fmsnfc02 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  fmspdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gpocont01 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  Gpodc153 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  GPODC51 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  gpodc52 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gpodc54 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gpodc55 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gpodc57 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  gpodc60 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gsddback PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  gsddfile1 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm0514 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm0515 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm0520 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm0524 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm0529 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm1521 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm2503 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  Hqmsadcm2504 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcmqct PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcmt206 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsappdc702 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsavnw70403 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsavnw7t202 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsbdcm1303 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsbdcm1305 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsbdcm1323 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmscdcm0511 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmscomcaldc704 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsdtp1dpsc240.prod.gpo.gov PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsdtp2dpsc240 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsedcm1333 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsedcm1335 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmswdcm0513 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmswdcm0518 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmswdcm1513 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  igbdc.ig.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  igpdc.ig.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  Image1 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  image5 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  image6 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  image7 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  image8 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  institute01.ifpep.gpo.gov PC WindowsXP 0 0 0 0 ?
Client/HW/OS/Pri:  ips_wrkflow PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  jasper PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  mars PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  Media1 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  mms-files PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  mms_pdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  msproject01 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  ofc_admin_bdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  ofc_admin_pdc PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  ofrpdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  operations-pdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  ophelia PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  ops-files PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  ops-pdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  oraasproda.fms.gpo.gov PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  oraastest PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  pearl2 PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  personnelpc8 PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  pluto PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  ppdbdc PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  presspdc.prod_press.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  prod_bdc PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  prod_server PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  qaserver1.qc.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  qc_pdc.qc.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  sgms PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  technet PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  zprodpc59.prod.gpo.gov PC WindowsNT 0 0 0 0 ?
Client/HW/OS/Pri:  webta_test PC Windows2000 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsddcm1716 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmsadcm1714 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  HQMSBDCM1712 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  HQMSBDCM1713 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmswdcm1219 PC Windows2003 0 0 0 0 ?
Client/HW/OS/Pri:  hqmswdcm1220 PC Windows2003 0 0 0 0 ?
Include:           ALL_LOCAL_DRIVES
Exclude:           (none defined)
Schedule:          Full
  Type:            FULL (0)
  Frequency:       7 day(s) (604800 seconds)
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  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
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     Offsite_Tape_Pool
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  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      018:00:00  082:00:00   138:00:00  202:00:00 034:00:00
   Saturday    000:00:00  000:00:00
Schedule:          Cumulative-Inc
  Type:            CINC (4)
  Frequency:       1 day(s) (86400 seconds)
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  Retention Level: 1 (2 weeks)
  u-wind/o/d:      0 0
  Incr Type:       DELTA (0)
  Alt Read Host:   (none defined)
  Max Frag Size:   0 MB
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     (same as policy volume pool)
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      018:00:00  034:00:00   042:00:00  058:00:00
   Tuesday     018:00:00  034:00:00   066:00:00  082:00:00
   Wednesday   018:00:00  034:00:00   090:00:00  106:00:00
   Thursday    018:00:00  034:00:00   114:00:00  130:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
Schedule:          User_Backups
  Type:            UBAK (2)
  Frequency:       7 day(s) (604800 seconds)
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  Retention Level: 1 (2 weeks)
  u-wind/o/d:      0 0
  Incr Type:       DELTA (0)
  Alt Read Host:   (none defined)
  Max Frag Size:   0 MB
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     (same as policy volume pool)
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      008:00:00  113:00:00   032:00:00  137: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  000:00:00
   Saturday    000:00:00  000:00:00

[KDOG1122]

Sorry I forgot to mention that I'm running NetBackup 6.5 Windows 2003 R2

[ahlip]

Reduce the frequency in your schedules to 6 days or below.

[Stumpr2]

and your daily backups frequency to 12 hours.

What these two suggestions will do is to ensure that the frequency requirement has been met when the windows first open. Also please remember that if a backup does not run and so you do a manual backup that it will then use the time of the manual backup to set the frequency. In other words for the full backups if they did not run on the weekend and so you run one Monday night then rven though the next window opens on Friday at 1800, the frequency will not be met until the next monday, (if you keep it at 7 days). So you can even bring the frequency down to 3 days. It won't hurt anything and it will ensure that at least the frequency requirement has been met by Friday night.

[KDOG1122]

I really appreciate you and taking the time to explain but I'm still not understanding the resolution you provide me.  Can you explain a little further? 

I'm not having any problems with my daily backups.  I'm only having problems with the full backups that occur over the weekend within a window of Friday 6pm - Mon 6am.  I only have four drives and need to backup 90 clients.  When the Full backup policy kicks off it starts to backup the clients but for some reason it doesn't queue the rest of the 86 clients but it will only queue about 30.

So how does changing the frequency to 3 days instead of 1 a week and changing the window gap to 12 hours do to correct this problem? 

[Stumpr2]

---

KDOG1122 wrote:

When the Full backup policy kicks off it starts to backup the clients but for some reason it doesn't queue the rest of the 86 clients but it will only queue about 30.

It queues 30 jobs. When do you eventually run the remaining 56 clients?

Most people if they see that the weekend job did not run then will attempt to run a manual backup on Monday. They want to get a full backup done for the week.

If you see that a full backup did not run on the weekend, will you try to run one on Monday or Tuesday to make up for it?  Most people do.

If you do run a full backup on a Monday or Tuesday then according to the 1 week (7 days) frequency, it will not want to run until 1 week has passed. So if you run a manual backup on Monday then it MUST wait one week before the next backup can run. That will put it to always want to run on a Monday. Right? Monday to Monday is one week.

When the window opens up to allow backups on Friday night only 4 days have passed since Monday night when you ran a full backup to cover the one that did not run on the weekend. Not enough time has passed for a weekly backup to run. 4 days is less than 1 week.

When Saturday comes the window is still open but there has only been 5 days since the last full bakup that you ran on Monday. 5 days still is less than one week so no backups will get queued.

When Sunday comes it has only been 6 days which is still less than a week so the backup job wil not be queued becaus only 6 days have passed since the last full backup.

Finally Monday comes and it has now been 1 week so a job could be queued. The problem now is that there is no open window for it to run. The window has closed.

To get around this problem make the frequency 3 days. Now when you run a manual backup on Monday you only need to wait 3 dys to look for an open window. The window finally opens on Friday night. Now you have met both requirements.

1. the frequency requirement of  3 days has been met.

2. the window opens up.

Since the frequency has been met and the window is now open then a backup will be queued.

Remember, both the frequency AND an open window must exist before the backup wil be queued.

Message Edited by Stumpr on 01-25-2008 08:32 PM

[KDOG1122]

Friday 6pm

Backup policy starts Full backup policy using a Four Tape Drive Library: The backup policy queues only 30 clients out of the 90.  The first four clients begin backing up (and the other 26 clients are in the queue waiting for the drive to become available).  Say these 30 clients will finish backing up around Saturday 8am.

Saturday 6pm

The same backup policy continues with the original backup policy that started on Friday 6pm but kicks off the next 30 clients.   The first four clients begin backing up (and the other 26 clients are in the queue waiting for the drive to become available).  Say those 30 clients will finish backing up around Sunday 9am.

Sunday 6pm

The last batch of the original backup policy continues with the original backup policy that started on Friday 6pm and kicks off the last 30 clients.  The first four clients begin backing up (and the other 26 clients are in the queue waiting for the drive to become available).  Say the last 30 clients will finish backing up around Monday 2am.

Now don't forget this is all within the same Full backup policy on the same Full schedule.  I don't know why it keeps putting a gap in between the same backup Full jobs.  So it will eventually backup all them up within the backup window but it puts 8-10 hour gaps in between.  I want it to run consecutively with no gaps.

I hope this helps! 

[Stumpr2]

change the frequency to 3 days and all will queue up at Friday at 1800

[KDOG1122]

Ok thanks!  I know I was a pain in the a** but thanks for helping me out.

[Omar_Villa]

what is the maximum jobs per policy you have set up under this policy? I think is not configured to start 90 jobs in the beggining probably only 30 jobs, then you get in under what Stumpr explain, just check that and change it to 90 and if you plan to change the policy to be able to run multiplestream you will need to increase that even more.

let us know.

regards

[Stumpr2]

Omar,

That was my first suspicion until Kdog posted this from bppllist

---

KDOG1122 wrote:

Max Jobs/Policy:   Unlimited

---

[KDOG1122]

I forgot to mention that changing the frequency option from 7 days to 3 days worked.

Thanks for your help!

[Stumpr2]

you're welcome