Exclude weekly backup during monthly backup

Calendar based scheduling wil be better suited for you.

You may do this as follows:-

1) Open your policy settings and go to "schedules" tab

2) Choose your "weekly" schedule , right click -> change

3) Under attributes choose "calendar"

4) Under "Edit calendar schedule by" choose "recurring week days"

5) Select all the days on friday except the last

6) Confirm that all Fridays get selected for all months except last.

7) Similarly create for Monthly schedule, just choose the last friday and dont select the reaming fridays..

regards..

All things being equal, you *should* find that schedules within the same policy should be able to cater for this without much (or any) intervention from yourself.

e.g.

Daily backup Mon - Sun retention 2 weeks

Weekly backup each Friday retention 4 weeks

Monthly backup last Friday retention 12 months

- all with appropriate frequencies and backup windows.

So obviously the last Friday of the month could potentially result in all three schedules being run.

However, if their backup windows are the same (same start time) then NetBackup *is* clever enough to work out which one to run based on frequency & last successful backup (and potentially retention).

One we *always* like to quote:

https://www-secure.symantec.com/connect/articles/netbackup-frequency-based-scheduling-1

I tried this method already. However, for example, Aug, it will run n the last week even I didn't highlight last week.....

If weekly and monthly backup run at the same time, it will run monthly backup first, but still weekly backup will run later.... We want the weekly backup not to be run while month end.....

Can you provide your policy details?

bppllist policy_name -U

------------------------------------------------------------

Policy Name:       abc01_ndmp

  Policy Type:         NDMP
  Active:              yes
  Effective date:      09/10/2010 15:21:12
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     50000
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           NDMP-ES-Daily
  Volume Pool:         Daily
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      0 seconds

  Granular Restore Info:  no
  Ignore Client Direct:  no
  HW/OS/Client:  NDMP          NDMP          abc01

  Include:  /vol/xyz01_dept
            /vol/xyz01_group
            /vol/xyz01_home
            /vol/xyz01_root
            /vol/xyz02_root
            /vol/xyz01_APPDATA
            /vol/CPH_N00_T2_01

  Schedule:          Yearly-Full
    Type:            Full Backup
    Maximum MPX:     3
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 12 (7 years)
    Number Copies:   1
    Fail on Error:   0
    Residence:       ENCR_NDMP-ES-LH-Yearly
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      SPECIFIC DATE 0 - 01/06/2012
      SPECIFIC DATE 1 - 01/04/2013
      SPECIFIC DATE 2 - 01/05/2013
      SPECIFIC DATE 3 - 01/06/2013
      SPECIFIC DATE 4 - 03/28/2013
    Residence is Storage Lifecycle Policy:     1
    Daily Windows:
          Tuesday    20:00:00  -->  Wednesday  06:00:00
          Thursday   22:00:00  -->  Sunday     00:00:00

  Schedule:          Weekly-Full
    Type:            Full Backup
    Frequency:       every 7 days
    Maximum MPX:     3
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (4 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       ENCR_NDMP-ES-LH-Weekly
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
      EXCLUDE DATE 0 - 01/06/2012
      EXCLUDE DATE 1 - 01/07/2012
      EXCLUDE DATE 2 - 03/29/2013
      EXCLUDE DATE 3 - 03/30/2013
      EXCLUDE DATE 4 - 03/31/2013
    Residence is Storage Lifecycle Policy:     1
    Daily Windows:
          Friday     20:00:00  -->  Monday     02:00:00

  Schedule:          Monthly-Full
    Type:            Full Backup
    Maximum MPX:     3
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 8 (1 year)
    Number Copies:   1
    Fail on Error:   0
    Residence:       ENCR_NDMP-ES-LH-Monthly
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      SPECIFIC DATE 0 - 04/30/2012
      Friday, Week 5
    Residence is Storage Lifecycle Policy:     1
    Daily Windows:
          Monday     18:30:00  -->  Tuesday    21:30:00
          Friday     20:00:00  -->  Monday     02:00:00

  Schedule:          Daily-Inc
    Type:            Differential Incremental Backup
    Frequency:       every 1 day
    Maximum MPX:     3
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       ENCR_NDMP-ES-Daily
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
      EXCLUDE DATE 0 - 04/30/2012
    Residence is Storage Lifecycle Policy:     1
    Daily Windows:
          Monday     20:00:00  -->  Tuesday    06:00:00
          Tuesday    20:00:00  -->  Wednesday  06:00:00
          Wednesday  20:00:00  -->  Thursday   06:00:00
          Thursday   20:00:00  -->  Friday     06:00:00

Ok.

Looking solely at the Weekly & Monthly backups there are two things, one of which *may* have a bearing on what you are seeing (maybe both)

1. The backup window is very large - is this actually necessary? Is there the potential that these jobs will not *start* at the alotted time of 2000hrs on a Friday? From my experience, if they do not start at about the same time there is the potential that both may run. Just for info, the window is only there as a time at which a backup can start (for *all* streams in a backup - queued jobs *will* fail if backup window closes) - it's not there to cover the whole time that a backup will progress to completion.
2. Frequency - drop the weekly one to 6 days or less (to a value larger than the backup window) - that means the job will be *waiting* to run at 2000hrs on a Friday - if it started a little later each week for whatever reason then a 7 day frequency will mean it keeps getting later & later ('schedule creep')

These are *potential* solutions .... not guaranteed.

You can also apply point 2 to your daily incrementals - change the frequency to 11 or 12 hours say - this will also mean that if the job fails then, if you do it in time, the job can be re-run & the next scheduled job will *still* kick.

In fact, the backup windows is not enough sometime as we have few TB need to be backup at weekend. Some backup jobs are fail because of exceeding backup windows at weekend, so that the backup windows is large.

I try to modify the schedule by running at first 3 weekend. Let see will it work better this weekend.

Turn on Multiple Data Streams to reduce the backup window.  Right now you are backing up seven volumes one after the other, rather than several at a time. 

It is a good idea! Thanks for your recommendation. However, I would like to ask if I turning on Multiple Data Streams in the policy, will the duplication of the policy use Multiple Data Streams too? If not, how can I configure the duplication using Multiple Data Streams too?