Edit 
/usr/openv/netbackup/db/class/CLASS_NAME/schedule/SCHED_NAME/info
file and put 1800 for the field FREQUENCY.

It is the number of seconds, after you save that file,
dont open that policy with GUI. 

Mike

--- Bob Stump <StumpB at michigan.gov> wrote:

> No problems in this post. I am just sharing a
> solution you may be looking for in the future J
> Scenario: I need to run a backup every hour on the
> hour and the backup lasts for about 15 minutes. 
> I've created the policy and schedule and set the
> frequency to 1 hour. The first backup runs on the
> hour, but the next schedule occurs one hour after
> the previous job ends and not from the original
> start time.  e.g. Job starts at 9:00, ends at 9:15,
> next job starts at 9:15 which is NOT on the hour.
> See the dilemma? Well, most of you already
> understand the concept of frequency creep. Obviously
> I needed to set a frequency that is less than 1 hour
> but, NetBackup has 1 hour as the shortest frequency
> interval for a schedule. My solution was to use the
> command
> /usr/openv/netbackup/bin/admincmd/bpplschedrep with
> the modification of *freq 1800. That set the
> frequency to 30 minutes (60 * 30) Funny thing is
> that the schedule still shows 1 hour frequency in
> the GUI. But that?s OK! The frequency of 30 minutes
> works great! No problems in this post. I am just
> sharing a solution you may be looking for in the
> future J 
> > _______________________________________________
> Veritas-bu maillist  - 
> Veritas-bu at mailman.eng.auburn.edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 



 
____________________________________________________________________________________
Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367