RE: Backing up RMAN catalog database

In our shop - we schedule a shutdown/cold backup of the rman repository
on a regular basis when we know RMAN  backups are not going to occur.
The backup of the RMAN repository takes very little time.
 
Steve Smith

Envision Technology Partners / MSHA MSIS Team

Desk: 303-231-5499

 

 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dennis Williams
Sent: Thursday, February 08, 2007 11:02 AM
To: fred_fred_1@xxxxxxxxxxx
Cc: Brandon.Allen@xxxxxxxxxxx; Thomas.Mercadante@xxxxxxxxxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: Re: Backing up RMAN catalog database


Fred,
 
What I've heard described is that if you have a very large site, you
could configure two RMAN backup systems (and catalogs). RMAN A backs up
half your Oracle databases and RMAN B's catalog. RMAN B backs up the
other half of your Oracle databases and RMAN A's catalog. When the tool
you own is a hammer, all the world looks like a nail. So of course the
RMAN developers are going to suggest using RMAN to backup RMAN's
catalog, after all, if they recommended another method, that might imply
that RMAN wasn't adequate for all your backup needs. 
    On a practical level, I think you need to evaluate what is right for
your site. What will provide the protection you need with the level of
effort in setting it up and maintaining it corresponding to the need. If
you are responsible for 200 databases, your approach may be different
than if you are only responsible for 2. 
 
Dennis Williams

Other related posts: