Re: Why I don't like RMAN repositories

From: Hans Forbrich <>
Date: Tue, 10 Dec 2013 10:16:44 -0700
Message-ID: <>

On 10/12/2013 6:18 AM, Dave Morgan wrote:
> Hi All,
> First off, if you are not properly backing up your control files
> then you
> will find yourself in trouble sooner or later. A repository will not
> help in that situation.
> If you are backing them up properly then you do not need a repository.

It all depends

Step #1 - get your requirements specification

If all you want from the backup is the ability to restore production to within the past day or so, and if you have sufficient safeguards on your control files such that the backup information therein is satisfactorily protected, then there is no real need to have a repository.

If that is the total requirement, then an external catalog repository is certainly a potential overkill.

Step #2 - look at contingencies, alternates, expanded needs

If you

- have a large number of databases and want consistent methods;
- have need or desire for 'readable' backup record information;
- have a need for long term (legal-7year) archive;
- have a need for external groups to request or even implement their own 
copy for development/test/training/tuning; - have need for centralized scripts, have need for additional and possibly cross-database backup analysis; then an external catalog repository might prove useful


Received on Tue Dec 10 2013 - 18:16:44 CET

Original text of this message