The trick with databases, in order to get the multiple retentions, is
to have (at least with Oracle + RMAN) RMAN send some values back to
netbackup to tell it which policy and schedule to use handle the
backup as. I think the values are NB_ORA_CLASS and NB_ORA_SCHED but I
could be off - I haven't had any need to do that in a while and the
scripts I had to implement it are at a previous job.

This is also needed if you have different databases on a host and
they're covered by different policies as the connect back to the host
will match the first policy that contains that host.

-Charlie 

On 6/11/05, David Rock <dave-bu AT graniteweb DOT com> wrote:
> * Kim Hennvall <kim AT hjemmekontor DOT nu> [2005-06-11 21:44]:
> > Hello,
> >
> > I might have been reading the original question wrong but i think Hampus was
> > thinking of online\hot backups and not file backups. When doing a
> > MS-SQL-Backup (ie) it will create a Default-Application-Backup retention,
> > schedule in the policy. This will not fire the backup from the client but it
> > will only tell the NB server for how it will store the backup, and when it's
> > possible to let the client run the backup. A daily, weekly or monthly
> > schedule is specified calling a BCH file (SQL specific) but this is only
> > letting the backup run during those hours. You can specify as many schedules
> > you like but it will still have the retention period of the
> > Default-Application-Backup "schedule".
> >
> > What happens is that the NB server fires off the scripts, the client will
> > then do a "user"-backup and this is logged with the
> > Default-Application-Backup. Since you only can have 1
> > Default-Application-Backup in each policy it will use that retention time,
> > and not the daily, weekly or monthly.
> >
> >
> > From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hampus 
> > Lind
> > Sent: 10. juni 2005 21:33
> > To: veritas-bu AT mailman.eng.auburn DOT edu
> > Cc: Fredrik Dahlberg
> > Subject: [Veritas-bu] database policy and several schedules...
> >
> > Hi all!
> >
> > Is there any smart way to have several schedules with different retention
> > (i.e incr_daily, full_weekly, full_monthly) within the same policy?? Or do
> > we need to seperate all these schedules to different policies still??
> 
> I don't see anything here about database-specific questions. This looks
> like a simple "can I have multiple retenitons" question to me. Mike's
> information is accurate and pretty descriptive of how it works. One of
> the inherent qualities of a policy is the ability to put a bunch of
> schedules with different retentions within it. In order to get
> appropriate behaviour from Netbackup, you _have_ to do it that way (an
> incremental schedule without a full schedule doesn't make any sense),
> and you would normally have different retentions on long-term fulls vs.
> incrementals.
> 
> Also to Mike's point about retentions, you need to make allowances for
> how your incrementals drop off. If you do fulls every day and they have
> a retention of 6 months, there's no problem, but if you are doing the
> fulls weekly and daily incrementals and the incremental retention
> doesn't coincide with the full, there will likely be gaps, so don't get
> caught in the trap of short-term retentions on incrementals and
> long-term retentions on fulls unless that really _IS_ what you meant to
> do.
> 
> --
> David Rock
> david AT graniteweb DOT com
> 
> 
>