> When it comes to overlapping schedules, set both schedules to run at
> the same time and the schedule with the longest retention will be
> the only one that runs. 

Actually that's the most common misconception in NetBackup.  With
frequency-based scheduling, more than one schedule due to backup, and
identical window-open times, the schedule with the longest _frequency_
setting will run; retention does not factor into this.  That is the
elegant mechanism by which an infrequent schedule (say, a yearly
backup) always wins when it's due, no matter how many monthly, weekly,
daily... schedules may also be due.  Those "lesser" schedules get
their turn at the next window opening, and again, ties go to the due
sched with the greatest frequency value.

This is why daily/weekly/monthly/quarterly/annual/... setups work
correctly without extra admin work.  Simple example:

test-policy

        daily-schedule,   cinc, freq 1 day,   0000-0400/7-days

        weekly-schedule,  full, freq 1 week,  0000-0400/7-days

        monthly-schedule, full, freq 1 month, 0000-0400/7-days

[add quarterly, annual, 5-year, ... scheds the same way]

Retention does not matter.  The daily above will run every day unless
it is trumped by a weekly which hasn't run in a week or a monthly
which hasn't run in a month.  The weekly as well as the daily will be
trumped whenever the monthly is due.  And so on up the _frequency_
hierarchy.  

Demonstrations of this are in the list archives.

> You can create a test policy and test this
> for yourself. So the yearly schedule should have a longer retention,
> than the monthly or weekly so the others will not run. Hope this
> helps.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu