08-25-2012 09:32 PM
Solved! Go to Solution.
08-28-2012 06:23 AM
full is always preferred over incr/diff from a backup engineers perspective.
08-26-2012 12:16 AM
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
08-26-2012 12:29 AM
monthly full has been scheduled to run on last saturday.i.e today.
But only monthly full ran today and not FULL
08-26-2012 01:10 AM
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.
08-26-2012 01:18 AM
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?
08-26-2012 01:25 AM
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.
08-26-2012 01:35 AM
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?
08-26-2012 01:49 AM
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
08-26-2012 01:50 AM
ok.So it does not depends upon the alphabetical order of the schedule?
08-26-2012 02:02 AM
No. it depends on what is inside the schedule - schedule type, frequency, open window, retention.
08-26-2012 05:43 AM
if in a policy ,both the schedule has the same ran last time ago,then?
How it depends upon schedule type?
08-26-2012 07:04 AM
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.
08-26-2012 08:07 AM
I am just asking the query,I wont do it anyway.
How it depends upon schedule type??
08-27-2012 12:37 AM
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...
08-27-2012 07:58 AM
so full is prefered over incr/diff,?
08-27-2012 08:31 AM
08-27-2012 10:55 AM
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
08-28-2012 06:05 AM
so full is prefered over incr/diff,?
08-28-2012 06:23 AM
full is always preferred over incr/diff from a backup engineers perspective.