I'd suggest doing a cold backup of the (small) recovery catalog database...
be sure to document it's location and contents in a README for DR purposes
(using automated machine characteristics script to keep current), so you
know which RMAN catalog goes with what (since they are release-specific).

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Sylvia Nergard
Sent: Friday, August 30, 2002 4:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Best practices to back up a recovery catalog (rcvcat)?


Hi list!

What is the "best practice" to back up the recovery catalog in this case?

I'm backing up Oracle Databases (online) with Tivoli Data Protection for
Oracle v2.2.1.
I have created a recovery catalog in an another database on the same server
as my target database
(I know that it is not recommended to have a recoverycatalog at the same
server as the targte database,
but because of costs I have no other choice).
Should I back up the recovery catalog online with TDPO, offline with TDPO
or regular filebackup???
Should the database with the recoverycatalog have its own recoverycatalog?
If so, can I use the target database (sounds little dangerous....)
or should I create a new database to content the recoverycatalogs
recoverycatalog?
If so how should I back up the recoverycatalogs recoverycatalog?
Should the recoverycatalog run in archive mode under all type of backups of
the recoverycatalog?

I'm new to Oracle and RMAN so I need some advice how to handle backup of
the recoverycatalog.......

Regards

Sylvia Nergerd
=