Re: difficult RMAN archivelog requirements

"hpuxrac" <johnbhurley_at_sbcglobal.net> wrote in message news:1108516262.444937.316520_at_z14g2000cwz.googlegroups.com...
> What's wrong with this (runs once a day or weekly whatever)
>
> step 1 ... crosscheck archivelog
>
> step 2 ... rman backup of just the archive logs "all"
>
> step 3 .... remove anything older than 1 day/week os utility / whatever
> ( may want to change criteria)
>
> step 4 ... crosscheck archivelog
>
> step 5 ... archive log current then rman backup of database include
> archive logs all ...
>
> Most people would advocate keeping 2+ days of archive logs on your
> system if you are doing daily backups, 2+ weeks on your system if doing
> weekly (depends on volume etc).
>

Certainly that can be done. I was looking for a RMAN one-liner backup command. But's that's OK. I to ended up with a couple of step process. I ended up querying v$archived_log and dynamically building the needed RMAN commands via an anonyomous PL/SQL block. Then wouldn't you know my manager changed the requirements on me.   Received on Wed Feb 16 2005 - 08:55:41 CST