Re: Database backups

as a rule of thumb u don't roll forward from a cold backup, (yes, yes I know you can but lets not get into bad habits)....

you can use just hot backups no probs and can recover quicker from them

pointers;

have multiple ctl files spanning physical disks multiplex your online redo logs across physical disks aim to log switch every 15 mins
every time you change the db structure "alter database backup controlfile to trace"
after the hot backup take a copy of the ctlfile and "archive log current" and make sure your archive redo logs are protected stream them off somewhere else every 15 mins
also when you take the hot backup keep a copy locally if enough space also stream to tape and if recovery time is an issue copy to some network storage

good luck

daniel...

"Dale DeRemer" <dderemer_at_agmc.org> wrote in message news:a7dcs8$q7u$1_at_malgudi.oar.net...
We are new the the Oracle world. We want our ebusiness server to be 7x24. Never, ever down. Meaning... no cold backups. So, our question is this: If we use hot backups, (RMAN), and never take a cold backup, will we be able to recover from any failure. Additionally, what is the impact, or difference in recovery time for a system with no cold backups, vs. one with a cold backup done once a week, or once a month?The DB is 75GB and will grow to about 100GB over the next year. It will be updated in batches from our mainframe. Users will not update it. Thanks for your help. Received on Thu Mar 21 2002 - 14:15:22 CST