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

Netbackup 6MP7 "Recurring week day" schedules wrong.

Created: 16 Aug 2010 | 4 comments

Hi..
Im after a bit of clarification on Netbackup's Reccuring weekdays scheduling option as we have been having issues this month.

We have weekly jobs that run on a sunday with 5 different schedules to direct the backups to the right media pool.. However so far the last two weeks these have failed.. i wasnt around to diagnose the failures last weekend, but this weekend i noticed that it had used the "Sunday2" schedule, despite the policy in the GUI showing that it was the Sunday3 schedule that should have run..

Does anyone have any ideas why its doing this?.. the only difference is we went up to MP7 from MP6 a couple of weeks ago, could this have changed the scheduling for recurring weekdays?. 

Heres one of the polices in question:

D:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist.exe System-Full-

-U
------------------------------------------------------------
 
Policy Name:       System-Full-Weekly
 
  Policy Type:         MS-Windows-NT
  Active:              yes
  Effective date:      06/17/2004 13:42:00
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     1
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Keyword:             (none specified)
 
  HW/OS/Client:  PC            WindowsNET    GMSDFM01
 
  Include:  System_State:\
            C:\
            D:\
 
  Schedule:          Sunday1
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (27 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Sunday1
    Calendar sched: Enabled
      Sunday, Week 1
    Daily Windows:
          Sunday     00:10:00  -->  Monday     07:10:00
 
  Schedule:          Sunday2
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (27 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Sunday2
    Calendar sched: Enabled
      Sunday, Week 2
    Daily Windows:
          Sunday     00:10:00  -->  Monday     07:00:00
 
  Schedule:          Sunday3
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (27 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Sunday3
    Calendar sched: Enabled
      Sunday, Week 3
    Daily Windows:
          Sunday     00:10:00  -->  Monday     07:00:00
 
  Schedule:          Sunday4
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (27 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Sunday4
    Calendar sched: Enabled
      Sunday, Week 4
    Daily Windows:
          Sunday     00:10:00  -->  Monday     07:00:00
 
  Schedule:          Sunday5
    Type:            Full Backup
    Maximum MPX:     10
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (27 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     Sunday5
    Calendar sched: Enabled
      SPECIFIC DATE 0 - 12/31/2006
      SPECIFIC DATE 1 - 04/29/2007
      SPECIFIC DATE 2 - 07/29/2007
      SPECIFIC DATE 3 - 09/30/2007
      SPECIFIC DATE 4 - 12/30/2007
      SPECIFIC DATE 5 - 03/29/2009
      SPECIFIC DATE 6 - 05/31/2009
      SPECIFIC DATE 7 - 08/30/2009
      SPECIFIC DATE 8 - 11/29/2009
      SPECIFIC DATE 9 - 01/31/2010
      SPECIFIC DATE 10 - 05/30/2010
      SPECIFIC DATE 11 - 08/29/2010
      SPECIFIC DATE 12 - 10/31/2010
      SPECIFIC DATE 13 - 01/30/2011
      EXCLUDE DATE 0 - 07/26/2004
      EXCLUDE DATE 1 - 09/27/2004
      EXCLUDE DATE 2 - 10/25/2004
      EXCLUDE DATE 3 - 12/27/2004
      EXCLUDE DATE 4 - 02/28/2005
      EXCLUDE DATE 5 - 03/28/2005
      EXCLUDE DATE 6 - 04/25/2005
      EXCLUDE DATE 7 - 06/27/2005
      EXCLUDE DATE 8 - 07/25/2005
      EXCLUDE DATE 9 - 09/26/2005
      EXCLUDE DATE 10 - 11/28/2005
      EXCLUDE DATE 11 - 12/26/2005
    Daily Windows:
          Sunday     00:10:00  -->  Monday     07:00:00
 
 
D:\Program Files\VERITAS\NetBackup\bin\admincmd>

Hope someone can help.

Ta
Colin G

Comments 4 CommentsJump to latest comment

Marianne's picture

There is something that I'm missing in this output:

Retries allowed after runday

Is this enabled?

I have seen this to cause 'unexpected' results. If 'Sunday2' was for some or other reason not successful and 'retry' is enabled, the unsuccessful schedule will be re-run next time there is an open window.

Explanation in Admin Guide of this attribute:
Enable Retries allowed after runday to have NetBackup attempt to complete this schedule until the backup is successful. With this attribute enabled, the schedule attempts to do run, even after a specified run day.

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

Col G's picture

Just checked, that option is not enabled for any of the affected jobs (from the windows gui)

Is there a commandline i can use to check?

Marianne's picture

I've just done a test - without the attribute enabled, bppllist does not display in output.
With attribute enabled, bppllist displays the following:
 Calendar sched: Enabled
   Allowed to retry after run day

You say that you were not around to troubleshoot. Is it possible that any of the following happened:
'Someone' kicked off manual backups and selected the wrong schedule?
'Someone' in the meantime realized the problem with 'allow retries' and have de-selected this attribute?

Any specific reason why you need to 'micro-manage' to this extend? Having this amount of volume pools introduce unnecessary complexity with media management. Why not just have one Weekly pool and keep an eye on Media Summary Report (verbose) to know when tapes will expire?

You don't actually even need to have separate Daily and Weekly pools, since NBU does not by default mix retention levels (daily and weekly schedules will automatically go to different tapes).

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

Col G's picture

I believe what happened last week  (from what i was told anyway) was the ops guys put in the wrong weeks tapes causing error 96..

Ive done a nbpemreq -predict for next sunday and it is showing that it *should* use sunday4..
If it doesnt work right again, i will re-create the polices and schedules as this usually solves strange scheduling issues.

I agree with you totally on the amount of micro-management.. its effectively a legacy config that heralds back way before my time when we had standalone tape drives and the operators just used tapes labelled mon, tues etc and it was never changed when they started using a library that supported barcodes.

We have a project on the horizon for a full backup review and upgrade to nbu 7 so im hoping to get a clean break and scrap the lot!..