In the attributes tab of the policy, there is a 'Job Priority'  filed, the greater the number the higher the priority of the job.

Regards,

Martin

I saw that tab but when we had a "professional" onsite about a year ago helping with the initial setup of this he said there was no real need to use that.  LOL! 

If i make the monthly job priority 2, weekly priority1 and daily priority0 will this only allow the monthly job to run the on the last day of the month even though a daily is scheduled at the same time? 

I know you kinda already answered that i just want to make sure my understanding is clear.  thanks

OK, I understand now - forget my answer, it is not the answers for your situation (now I understand what you are doing ).

This of the 'Job Priority' as a method of getting a 'restore' or 'backup' to run ahead of other jobs.  It is not there to prevent a job from running.

If you take one of you jobs, that has a Daily/ Weekly/ Monthly schedule, tell us some more details  ...  in fact just run ...

bppllist <policy name> -U

I'm after details such as if this is a calander or frequency based schedule ...

I think the correct answer, taking into account how NBU works ... is that you shoudn't have backup windows that 'overlap' for the same policy.

If the backup window for each schedule opened at exactly the same time, AND, the monthly backup has a longer retention period, i think this would be the one that ran - as the higher retention will get the priority, however, I have no idea what happens if the backup windows only 'slightly ' overlap for example.

I know what the answer will be if I go and chack with a backline engineer, and that will be that as above, don't overlap schedule  windows for the same policy.

Martin

In addition to my post above about using claendar scheduling, Martins response has reminded me to ask you to make sure that you set the retention period for your backups on the Default-Application schedule and not on your own schedule - or you backups will dissapear sooner that you expected! - hence the reason for having three policies.

Sure you already knew that and it is the reason for the three policies but it is worth jogging your memory!

Hope this helps

I sometimes and not the best at explaining what im after on these forums but yes i am trying to make a daily/weekly not run if a monthly is due on that day.

All of my policies (except SQL) are setup with multiple schedules using slps for retention in the single job:

daily: frequency based (1 day) with a 1 month retention

Weekly:Calendar Based (Saturdays) 2 month retention

Monthly:Calendar based (last day of month) 7 year retention

The policies setup with these schedules do work as designed by the retentions.  a daily or weekly will not run if a monthly is scheduled for that day.

The SQL polices which are all individual jobs based off of the schedules above will kick of a daily on the same day as a monthly

Mark what you described above is kinda what i was hoping to avoid.  I guess im just trying to be lazy and keep as much manual configuration out as possible. But it appears that anything to do with a sql backup is all manual with netbackup. 

you think its just as easy if i go in and exclude the last day of the month for my daily and weekly policies?

If you set the schedules up as i have explained above it only takes a few minutes to do them all and you dont need any exclusions

It is probably less work than you have already done in your current ones to be honest and you never need to worry about two of them running at the same time.

If you do exclusions you will need to set 12 for each year - no need for any of that with my method

That makes sense.  You are very right.  I have probably made this so overly complicated it aint even funny.  My boss ask me every week what im working on and it feels like i have been telling him netbackup now for over a year.  I just cant seem to get this thing fine tuned.

It keeps me employed.  LOL.

Thanks again for all the help.  i will work on getting my schedules setup.

Great - once you have it cracked and are happy dont forget to mark a post as a solution if you feel you can to assist other in the future

Mark,

I had a thought i would like to run by you. Below is the schedule i was thinking about.

Daily's (incrementals): Sun(pm) - Sat(Am) Calendar based

Weekly's (Fulls): 2nd, 3rd, 4th, last Sat(pm) - Sun(am) Calendar based

Monthly's (Fulls): 1st Sat(pm) - Sun(am) Calendar based

My daily and weekly backups go to some 5200 appliances.  Monthly backups go directly to tape and are taken offsite

If a monthy backup runs on saturday are the incremetals that run the following five days based off of that monthly full backup?

http://www.symantec.com/business/support/index?page=content&id=TECH32563

Thanks for the link.  All of my other backups are setup this way 

Stanley

Your issue here is "Sat(pm) - Sun(Am)" - When using calendar based schedules Saturday and Sunday are different days!

You need it to start early enough on a Saturday to have at least started running before midnight or start it just after midnight (so your day would actually be Sunday)

You cannot cross midnight with calendar schedules as they are 2 different days

You could use "retries allowed after runday" but I would advise against it as it can cause unpredictable results and could could two polcies to run at the same time which you are trying to avoid here