Originally posted by marist89
In your situation, I would plan on a daily hot backup. You could limit the growth of your log_archive_dest by running several archivelog backups to tape or NFS disk throughout the day and removing them once they are backed up. However, not having your archived redo logs on disk will severely limit your chances for a quick recovery.
Totally agree. However, it may be better to have a "not so quick" recovery than "no recovery" at all. According to my estimates, a full recovery would take 12+ hours.
What about NFS? Based on your experience, would you recommend it? Personally, I had some problems on NFS mounting/umounting due to its persistency nature. Maybe just ignorance of mine, never tried it on Oracle myself.
You may think about using RMAN.
You will then alter the database to applied archivelog.
With RMAN you have the availability to perform Hot Backup to tape.
With RMAN you can run a script that backups all the archivelog periodicly and clear them from the disk.
Oh, I forgot to tell... Not 9i. Not even 8i. I think I'll shoot my head 
Our 9i databases already use RMAN with ARCHIVELOG and happilly they aren't an issue for now.
Last edited by adrianomp; 04-13-2004 at 02:15 PM.
An ounce of action is worth a ton of theory.
—Friedrich Engels
Reply With Quote