Your points about having one class and multiple schedules with different
retention periods is valid, however in the case of Oracle / Netbackup it
doesn't appear to be possible.  (Someone feel free to tell me otherwise.) I
do remember the first time I implemented an rman with Netbackup solution,
that I wasn't sure what the heck this "default-policy" job was that always
ran.  I would have to check my notes on why this is used, but I believe it
had something to do with the way Netbackup scheduled rman jobs.

Anyway the different schedules / retentions periods would work for an OS
backup, but as far as I know you will need to implement the different
classes for your Oracle backups if you want different retention periods for
each of the schedules.


Dan


-----Original Message-----
From: Ballowe, Charles [mailto:CBallowe AT usg DOT com]
Sent: Thursday, September 06, 2001 3:52 PM
To: 'Sixbury, Dan'; Ballowe, Charles
Cc: EBU (E-mail)
Subject: RE: [Veritas-bu] Oracle Backup question




> -----Original Message-----
> From: Sixbury, Dan [mailto:sixbury AT celeritas DOT com]
> Sent: Thursday, September 06, 2001 3:27 PM
> To: 'Ballowe, Charles'
> Cc: EBU (E-mail)
> Subject: RE: [Veritas-bu] Oracle Backup question
> 
> 
> When you initiate the oracle backups, are they being scheduled from
> Netbackup, or are you using cron on the server to run the 
> local rman scripts
> which use the class and schedules that you mention?  

Netbackup is handling the schedules -- I'm kicking them off as manual
backups as I test things.

> So far as seeing default-policy running when you perform the 
> Oracle rman
> backups, you always see the default-policy as running when 
> you initiate a
> Netbackup for Oracle / RMAN backup.

Ok -- any reason this is the case, or is it one of those things that "just
is"?

> I wasn't sure about the retention periods, but if you are 
> needing different
> retention periods for your backups you may want to set up 3 
> classes assuming
> that you want different retention periods for all three schedules. 

Isn't that what the retention period in the schedule is supposed to
accomplish? It just seems cleanest to kick off the backups from one class
(per database instance). If a class for each retention period is what needs
to be done, then I can do that, but it just feels like a work-around.

-Charles Ballowe
 
> 
> Dan
> 
> -----Original Message-----
> From: Ballowe, Charles [mailto:CBallowe AT usg DOT com]
> Sent: Thursday, September 06, 2001 3:03 PM
> To: 'veritas-bu AT mailman.eng.auburn DOT edu'
> Subject: [Veritas-bu] Oracle Backup question
> 
> 
> I'd like to have a class for oracle backups with 3 schedules 
> in the class. A
> monthly 
> (every 4 weeks) cold full, a weekly hot full, and a nightly 
> hot cumulative
> incremental. I have a script that calls the appropriate rman 
> information
> based on the NB_ORA_PC_SCHED 
> variable in its environment when it's called. This works and 
> performs the
> appropriate type of backup, but the jobs that actually write 
> to tape show up
> as being in the default-policy. This, of course, doesn't work 
> out because
> the retention periods that go with the schedules aren't gonna take.
> 
> If I put the 'send' command into the rman script, I end up 
> with an error 240
> "No schedules of the correct type exist in this class".
> 
> Any ideas what I might be doing wrong?
> 
> -Charles Ballowe
> 
> Platform:
>       NBU 3.4 DataCenter
>       Tru64 5.1
>       SSO
>       Oracle 8.1.7
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>