Re: RMAN questions

I agree that 30 days is fine, for most circumstances. And in my systems, the entire database gets backed up in 30 days. But we like to keep multiple generations of backups around, just in case. You can call it the "old-school ways" if you like from back in my mainframe days. And sprinkle in some paranoia. What if I for some reason, the tape holding my last backup has a bad spot? Then it would be nice to be able to go back to the previous backup, or the one before that. Which is why we have a 90 day retention policy in place.

But even if it wasn't 90 days, then substitute "30" instead of "90" in my previous post. The concerns are still the same from my point of view.

Cheers,
Brian

Sybrand Bakker wrote:
>
> On Wed, 25 Jun 2003 20:41:59 GMT, Brian Peasland
> <oracle_dba_at_remove_spam.peasland.com> wrote:
>
> >Personally, I wish that
> >they'd just let me remove stuff that is 90 days or older. And why do I
> >have to perform a crosscheck? Shouldn't I have to power to just remove a
> >backup set if I deem it is no longer necessary?
>
> I'm not sure whether I want to be capable to go back and roll forward
> for 90 days for the databases I am using RMAN on. That would pose a
> real disaster as all databases are interrelated *on application*
> level, and I would be forced to roll forward 8 databases for 90 days.
> I think for most purposes 30 days is fine, and requiring to go back
> longer is just for people who want their DBAs to retire.
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address

-- 
===================================================================

Brian Peasland
oracle_dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"