schedule confusion

[NIKHIL234656595]

I have a policy nik23

in which i have 3 schedule Full,Monthly-Full,INCR.

FULL and Monthly full(calender)  has same day and time window on a specific saturday

Which will trigger?

Policy Name:       nik23

  Policy Type:         MS-Windows

  Active:              yes

  Effective date:      08/11/2012 14:00:34

  Backup network drvs: no

  Collect TIR info:    no

  Mult. Data Streams:  no

  Client Encrypt:      no

  Checkpoint:          yes

       Interval:       15

  Policy Priority:     99999

  Max Jobs/Policy:     Unlimited

  Disaster Recovery:   0

  Collect BMR info:    no

  Residence:           bc-xgi-full

  Volume Pool:         NetBackup

  Server Group:        *ANY*

  Keyword:             (none specified)

  Data Classification:       BC

  Residence is Storage Lifecycle Policy:    yes

  Application Discovery:      no

  Discovery Lifetime:      0 seconds

  Include:  ALL_LOCAL_DRIVES

  Schedule:          Full

    Type:            Full Backup

    Frequency:       every 4 days

    Daily Windows:

          Saturday   13:00:00  -->  Sunday     06:00:00

  Schedule:          Monthly-Full

    Type:            Full Backup

Calendar sched: Enabled

      Saturday, Week 5

    Daily Windows:

          Saturday   13:00:00  -->  Sunday     06:00:00

  Schedule:          INCR

    Type:             Incremental Backup

    Frequency:       every 12 hours

    Daily Windows:

          Monday     19:30:00  -->  Monday     22:30:00

          Tuesday    19:30:00  -->  Tuesday    22:30:00

          Wednesday  19:30:00  -->  Wednesday  22:30:00

          Thursday   19:30:00  -->  Thursday   22:30:00

          Friday     19:30:00  -->  Friday     22:30:00

[revarooo]

your full will run every Saturday. your monthly full will only run on saturday of week 5.

BOTH full and monthly full will run on saturday of week 5. if saturday falls on a week 5

[NIKHIL234656595]

monthly full has been scheduled to run on last saturday.i.e today.

But only monthly full ran today and not FULL

[Marianne]

That is good. That shows that NBU is intelligent enough to only run schedule with longest retention when two shedules are due at the same time.

Some things can only be known for sure by testing it - like you have found out now.

This NBU behaviour is probably documented somewhere, but finding things out through experience is also good. 

[NIKHIL234656595]

ok Now i got it.In case there are two different policy A and B with same start and end window and same monthly full retention ,then who will run?

[Marianne]

Two different policies will both run if each of them has a schedule that is due. 

Each policy is cheched separately. Only schedules within SAME policy are evaluted when NBU needs to determine when to run.

You can use 'nbpemreq -predict_all -date <mm/dd/yyyy HH:MM:SS>' to verify.

[NIKHIL234656595]

ok.LETs suppose i have a policy in which i have 3 schedule INCR,FULL,MONTHLY FULL with same start time and end time and all have same retention of 4 weeks.What in that case?Which will run then?

[mph999]

I would image the one with the longest retention.

If two of the schedules have the same retention, then the one the was run the longest time ago.

If you run nbpemreq -subsystems 1 screen - it will tell you which run is next due to run, and why.  The output is quite /messy, but if you look you will see that for every client/ policy there is a section.

Martin

[NIKHIL234656595]

ok.So it does not depends upon the alphabetical order of the schedule?

[Marianne]

No. it depends on what is inside the schedule - schedule type, frequency, open window, retention.

[NIKHIL234656595]

if in a policy ,both the schedule has the same ran last time ago,then?

How it depends upon schedule type?

[revarooo]

Question, why would you backup exactly the same data twice, one on calendar and one on frequency based schedules?

If you wanted to duplicate the copied backups, use SLPs.

[NIKHIL234656595]

I am just asking the query,I wont do it anyway.

How it depends upon schedule type??

[mph999]

I have absoluely no idea ... so I ran a test, to show you what you can do to work things out.

One standard (unix) policy, three schedules set to run 1 per day, and retention for all of them as 1 month.

I set the backup window for all of them to Mon  08.30 - 11.30 and let it run ...  When it finished, I waited a few mins to be sure nbpem recalculated when it would next run

I then ran nbpemreq -subsystems 1 screen

You find the jobs by looking for the <policyname/ <clientname>

PolicyClient::test4/womble Task

... then look down until you find this bit...

  PolicyClient::test4/womble Task

  Schedule calculation delay: 0:01:00 (60)

  Client offline: false

  Active: true

    Scheduler::test4/womble::0

    Scheduling calculation made at: 2012/08/27 08:33:55 (1346052835)

    Stream's earliest times based on failure history

      0: Not a factor

    Next schedule to run: full

      Due: 2012/09/03 08:30:00 (1346657400)

      Start: 2012/09/03 08:30:00 (1346657400)

      Window closes: 2012/09/03 11:30:00 (1346668200)

      Reasoning:

        incr::0: Only/first schedule checked, DT=2012/09/03 08:30:00 (1346657400), RST=2012/09/03 08:30:00 (1346657400), WCT=2012/09/03 11:30:00 (13

46668200)

        diff::0: Ignored, previous schedule type better/same, DT=2012/09/03 08:30:00 (1346657400), RST=2012/09/03 08:30:00 (1346657400), WCT=2012/09

/03 11:30:00 (1346668200)

        full::0: Has better schedule type than previous, DT=2012/09/03 08:30:00 (1346657400), RST=2012/09/03 08:30:00 (1346657400), WCT=2012/09/03 1

1:30:00 (1346668200)

So, we see it will next run the Full schedule, as NBU thinks a Full is 'better' than any type of incremental, even though, it has just run a Full backup.

I don't know what the NBU logic is, I don't need to know - if I run nbpemreq -subsystems 1 command, it tells me why it is going to run then next schedule.

Martin

[NIKHIL234656595]

so full is prefered over incr/diff,?

[NIKHIL234656595]

<admin_dir_path>nbpemreq -subsystems [screen] depth [list | all |

subsystem_id...]

What if i want to see for a particular client and policy?

[mph999]

You can't - you have to run the command and probably best to output it to a file.  Then you look through it till you find what you want.

So, the 'start' of the section is like I showed as before:

PolicyClient::test4/womble Task

This would be the for the client 'womble' in the policy test4.

the section about when it will next run , will be somewhere between the 'start' of the section and the start of the next one.

If there are many policies and clients, then the command :

nbpemreq -subsystems 1 screen will not show all the output, it gets 'truncated' and there is nothing taht can be done about this.

In this case you have to run:

nbpemreq -subsystems 1  (without the word screen)

... then ALL the output is sent to the nbpem log, and you can view the nbpem log to see the details.

I think you should be fine though, I do not often see systems that have that many clients/ policies.

Martin

[NIKHIL234656595]

so full is prefered over incr/diff,?

[revarooo · Accepted solution]

full is always preferred over incr/diff from a backup engineers perspective.