Re: What are the common mistakes DBA do retarding backup & Recovery?

> 3. Afraid of using RMAN or Making benefits of RMAN

I would like to challenge Pt 3 in the OP's list.

It is NOT an issue if RMAN is NOT being used. There are databases that are hundreds of Gigs in size that are backed up from split mirror disks (Mirror database disks, place whole database in backup mode, split the mirror, take the database out of backup mode, switch the redologs, mount the mirror filesystems under a separate tree, transfer the new archivelog to the mirror's archivelog directory, backup the mirrors, and you are done). Although there is a cost (extra $$ for the mirror disks) there are some advantages:

1. You have a backup of the database online in the mirror (until at least the time you are ready to merge the mirrors back) - this has saved my behind in one specific case on a highly visible system. No mucking around with RMAN's MML and tapes or even a disk stage - just a straight copy of datafiles back into the original area)
2. You take the backup I/O away from Production datafiles (RMAN contends with the live datafiles)

Backing up an Oracle database without regular scheduled restores (from tapes if possible) as well as NOT backing up the Application tiers along with the database are high in my list of common mistakes. Again, for SOX compliant organizations, this is usually an IT Control so many orgs have become better at this (one of the positive effects of SOX)

-- 
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)

** The opinions and facts contained in this message are entirely mine
and do not reflect those of my employer or customers **
--
http://www.freelists.org/webpage/oracle-l