Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: backing up rman catalog for disaster recovery

RE: backing up rman catalog for disaster recovery

From: Marquez, Chris <cmarquez_at_collegeboard.org>
Date: Wed, 25 May 2005 08:22:22 -0400
Message-ID: <B30C2483766F9342B6AEF108833CC84E0450BBB9@ecogenemld50.Org.Collegeboard.local>


Paula,
I do this in my shell script *every* time and AT THE END OF EACH BACKUP I run...FULL, ARCH ONLY, etc. Even if I have a local Recovery Catalog.

Effectively I now have a current controlfile (Recovery Catalog so to speak) on my remote server or at least a copy on the local server. A current controlfile *COPY* is better (to me) than any Recovery Catalog.

NOTE: This is NOT an RMAN *backup* of my controlfile (totally useless), but rather a *COPY* of my controlfile. Meaning it can be used without RMAN; I cna $>cp controlfile.bkp controlfile01.ctl with this COPY.

A current (after backup taken) controlfile *is* a catalog...I now have a "catalog" backup with the same information that is in the Recovery Catalog. :o)

Even when I have a full blown Recovery Catalog I have never (had to) use it or restore it to another server...this controlfile COPY is always my first and faster option to get my DB up on a remote server in a disaster.

Try it...mount this controlfile (with another instance) and do RMAN list backup without connection to the real Recovery Catalog.

hth

Chris Marquez
Oracle DBA

#!/bin/sh
#

...

# - Backup controlfile and spfile.
# - Even though you have one in the back it IS BETTER to have one all by itself.
# - THE ONE WITH THE BACKUP DOES *NOT* HAVE CURRENT BACKUP INFO!!!!!
run {allocate channel c4 type disk;

     copy current controlfile to '${bkp_dir}/${date_time}_${DATABASE_NAME}_controlfile.ctl.bkp';
# - 8i
# sql "alter database backup controlfile to trace";
# - 9i

     sql "alter database backup controlfile to trace as ''${bkp_dir}/${date_time}_${ORACLE_SID}_trace.ctl.bkp''reuse";
     release channel c4;

    }

...

scp ${bkp_dir}/${date_time}_${DATABASE_NAME}_controlfile.ctl.bkp oracle@${Node3}:${bkp_dir_Node3}/ >> $log_file 2>&1

-----Original Message-----
From: oracle-l-bounce_at_freelists.org on behalf of Paula_Stankus_at_doh.state.fl.us Sent: Wed 5/25/2005 4:48 AM
To: Paula_Stankus_at_doh.state.fl.us; rgramolini_at_tax.state.vt.us; all_about_oracle_at_hotpop.com; oracle-l_at_freelists.org Subject: RE: backing up rman catalog for disaster recovery  

I am setting up a disaster recovery site and I was thinking about the best way to do this.

My theory is that I would like to not just use another recovery catalog on the DR site to backup my primary catalog but to somehow keep these catalogs constantly in-synch so when I do need to do complete recovery and only have the secondary rman catalog available - I wouldn't have to recover the catalog as all of the previous backups would be found there.

So....should I do this using Oracle Data Guard on my disaster recovery site catalog or backup rman then restore as my first procedure? Any advice? =20

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






--
http://www.freelists.org/webpage/oracle-l
Received on Wed May 25 2005 - 08:27:12 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US