Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: rman backups

RE: rman backups

From: Michael Fontana <>
Date: Wed, 8 Nov 2006 09:28:12 -0500
Message-ID: <>

While I don't have any production databases running in NOarchivelog at the present time, I actually found one, which had been setup by a vendor consultant, and just switched it over very recently. Except for an export (which failed quite a bit), this database ran totally unprotected.  

How does management allow this? By hiring a subject matter expert (in this case, a vendor consultant) who knows alot about an application but nothing about databases. It was his job to "get it running", not to consider the database or recoverability. After all, he would be long gone before such issues came up. How did it keep running in this fashion? No one wanted to touch it, and management didn't support anyone messing with it, and the even 5 minutes of downtime it eventually took to do the work.  

I eventually overcame this when a datacenter outage caused the server to be down. I was so sure archivelogging was the right thing to do, I implemented it, and then just told management it was done in my next status report. I used their resistance to change to my advantage - if they would not allow an outage to turn it on, they now could not justify, with their own line of thinking, an outage to turn it back off.  

I call this style of management "misapplication of the facts". Or the "if no one's complaining but the DBA, then it ain't broke" concept. I run into it alot. It's the "A" in dba that causes me to resist!  

Good luck with your problem...  

Michael Fontana
Senior Database Administrator

From: on behalf of goran bogdanovic Sent: Wed 11/8/2006 5:59 AM
Cc: oracle-l
Subject: Re: rman backups

On 11/8/06, Mark Brinsmead <> wrote:

        To take Bob's comments one step farther...         

        If your data is worth the trouble of backing up, archivelog mode is (almost) mandatory.         

        Does your management understand that doing offline backups (without archivelogging -- after all, cold

I have seen such "managers" is sad that such people are managing production systems...I just wonder how they get to this position?

        backups don't preclude archivelog mode) leaves you in a position where a serious system failure (maybe coupled with one bad tape cartridge) could cause you to lose several days' worth of data? Are they okay with that?  

        The incrementa cost of running in archivelog mode is (for most organizations) a nit compared to the risk of operating without it.                  

        On 11/7/06, Bob <> wrote:

                Hi Brian, Im surprised no one has mentioned that backing up with rman in no archive log mode will give you nothing more than an rman managed cold backup.                 


                Maybe you "cant" run in ALMode (management reasons) but if your goal is to "...become more intimate..." with rman- then archivelog mode is mandatory. The good thing about using rman is that it manages (deletes obsolete, applies recovery) of archive logs for you. Minimal manual intervention is needed to manage, or apply archive logs                 




-- Mark Brinsmead
Senior DBA, The Pythian Group
Received on Wed Nov 08 2006 - 08:28:12 CST

Original text of this message