What is the recommended method for backing up the RMAN repository?
• It should be a separate database, not contained in any of the target databases whose backup data it contains. • Create a new shema in the Enterprise Manager Database to house the Recovery Manager catalog • High availability of the catalog can be achieved by any of the following techniques: • standy database • replication • maintaining two separate Recovery Catalog databases: one is kept in sync as it is used for everyday production operation, and the other is kept in sync manually, by periodically issuing the RESYNC CATALOG command. • Use RMAN to back up the Recovery Catalog database, but for these backups, start RMAN with the NOCATALOG option, so that the backup repository for the Recovery Catalog is its own control file. The CONTROL_FILE_RECORD_KEEP_TIME parameter should be set to a value which is high enough to store an adequate amount of historical backup data for the Recovery Catalog. • Back up the Recovery Catalog controlfile, so that you can restore it if you ever need to rest
