Re: Question: Backing up online databases

sjs_at_shell.portal.com (Steve - Schow) writes:

> Hi all,
>
>We have a situation where we need to have oracle running 24 hours/7 days
>a week and we need to obviously keep the thing backed up. I have been
>pouring through all the books trying to figure out the strategy for this,
>and there seems to be little mentioned about this scenario. Apparantly most
>people don't need to do this.
>
>Anyway, what is the best strategy for this?
>
>If I understand correctly, you must backup your tablespaces one at a time
>and then backup your control files. This can all be done while the database
>is up and running. The redo logs CANNOT be backed up while the system is
>running.
>
>Now then, If you can't back up the redo logs, then what does that mean will
>happen when the system crashes and I have to restore?
>
>Basically, what I need to know is a good strategy to provide full recoverability
>of an oracle database that never gets shutdown(or if it does, only once a
>month or so for a few minutes).
>
>-steve
>
>--
> __ __
>__ ( _/_ _ ( _ /
> __)/(- \/(- __)( /)()((/
>

You cannot back up your redo logs, but you can mirror them and use archiving. Archiving redo logs automatically copies the logs to some device (preferably a different device) as soon as the log fills up. Mirroring the redo logs is supported through the RDBMS kernel and will write multiple copies of each log simultaneously. The different redo logs should be stored on different devices. Combining this with online tablespace backups and online control file backups will give you 24x7 availability.

Darin Brown
Oracle Commercial Consulting Received on Tue Nov 08 1994 - 17:47:50 CET