Treat the control files just as you would any other critical DB file. When you shut your DB down and snapshot it, make a backup copy of the control files also. Control files only change when you do structural changes to your database, and thus must be backed up only then. Of course that is best case, just incorporate control files into your normal backups. As for redo logs they do not nee to be backed up. In fact you really cannot use them for anything other than instance recovery when you have the database crash. If you do a clean shutdown there is no data in these redo's. It gets flushed to disk during the shutdown.
I would also recommend not putting redo's on your netapp, it is just an incredible waste of I/O. Buy some cheap 4G drives and install them. If you multiplex your redo's you should not have to worry about disk failures.
--Brian
X X gynt@post.com 08/11 3:42 AM >>>
- Does a hot backup (as described on
http://www.netapp.com/tech_library/3049.html) present any restoration problems? Has anyone done a restore from a hot backup?
How about handling of the control files? In other hot-backup schemes I have seen, there are a lot of stuff on how and when to do the "ALTER DATABASE BACKUP CONTROLFILE ... ..." command.
Also also some stuff on "ALTER SYSTEM SWITCH LOGFILE" or "ARCHIVE LOG NEXT"
None of these are mentioned in the above TechLibrary article.
/Gynt
______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup