Re: RMAN Retention policies

Hi Mike,

Yes, it is the way to go.
If these are cold backup, it will work flawlessly.

Otherwise, I observed that the LOG parameter of the KEEP option was buggy (our version was Oracle 9i, I can't remember the exact release): while the docco said that LOG would keep the archived logs needed to make the online backup consistent, in fact it kept *all* logs backed up after the related backup.
So KEEP was not suitable for online backups.

Regards,
Jerome

On 10/21/05, Mike Schmitt <mschmitt_at_uchicago.edu> wrote:
>
> Hi all,
>
> I was wondering if I could get some advice on the best way to handle
> retention policies as they relate to RMAN and media management
> software. This is for a mixed 9.2 and 10 environment.
>
> For example, if we wanted to implement a retention policy that looks like
> the following, and has all other backups removed from the tape library.
> - Keep daily full backups for 1 week
> - Keep full backups taken on Sunday for 1 month
> - Keep 1 backup from every month for 1 year
> - Keep all archive logs for 30 days
>
> I am curious about what others do to handle this? Would it be best to set
> a keep time for each backup that gets run, designating how long that
> particular backup should be retained, or would it be better to have a
> separate script log in and change the catalog to match what you want the
> policy to look like. ( This is for TSM btw, and my impression is that TSM
> mainly leaves retention up to the commands it gets by way of TDP)
>
> I am currently leaning towards handling this with the keep option, but I
> would appreciate any advice
>
> Thanks
>
>
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l