Re: Backup Tool Alternative to RMAN and BMC's SQL Backtrack

Thank you for your helpful reply, I appreciate it.

May I ask you more about using RMAN, since I have concerns about using and maintaining it.

Oracle Metalink seems to regularly issue patches/fixes for RMAN. Since RMAN is within $ORACLE_HOME do you need to shutdown Oracle in order to applyand relink software fixes? How often do you do apply fixes and how much work/time does it take you to review the patches and stage them through your system landscape? How many separate installs of Oracle do you need to maintain for RMAN?

How many Catalog databases (RCAT) do you use? Where are they hosted, on the same or on different server from the target database? Do the Catalogs ever get corrupt or have other problems that complicate the use of RMAN.

Do you need to have separate Catalogs for separate version of Oracle? Do you use a naming convention to distinguish these to make then easier to manage?

If RMAN aborts for any reason do you have to deal with manually cleaning up processes, enqueues, etc? How are you notified of an RMAN failure.

How often do you use RMAN to restore a database to another server and rename the SID? Have you done a PITR using RMAN and many archives? How did you manage the disk space requires of the archive directory during that process?

And lastly, thank you for not making some asshole assumption that I would spend my company's money because I can't or won't open OEM.

Thank you. Received on Wed Feb 23 2005 - 17:04:19 CST