| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Question of degrees in Oracle DB recovery
Having had to do this a couple of times:
First things first, during database creation, don't put database files = and the online redo logs (or control files for that matter) on the same = disk drive. The weakest hardware point in your system are the drives, = moving parts enough said? Next as several others have stated, make sure = your in archive log mode. Being in no archive log mode is the same as = saying I'm not planning on a disaster (deny the existence of Murphy & = your asking for it). Then place the archive log destination somewhere = else in the file system, yeah yeah another disk drive away from all of = the above. After you've got those setup then make a COLD backup as a = starting point, and hot backups thereafter. Make sure to keep archive = log files for slightly longer than backups. If you keep backups around = for 60 days keep the archive log files around for 70 days. It also = helps to mirror everything is possible & stay away from stripping. = Haven't had a good experience with that beast, yet.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Wolfe Stephen S GS-11 6 MDSS/SGSI
[mailto:Stephen.Wolfe_at_macdill.af.mil]
Sent: Tuesday, June 29, 2004 12:00 PM
To: oracle-l_at_freelists.org
Subject: Question of degrees in Oracle DB recovery
First off, I'm an Oracle newbie for sure. My main question now is more
DR policy/intent
Oriented than technical. I'm still in the discovery process of all the
ways an Oracle instance can be recovered, I'm now reading a PDF on
online point-in-time recovery strategies and this is where I have a
question.
How many of you guys provide as close as possible to the transaction-on-the-fly point-in-time recovery?
Currently, we do only an offline, once a day backup to a SAN on two Oracle applications. I was asked last Friday if we had a catastrophic failure (server destruction or totally non-recoverable disk failure) how would I recover our TPOCS database. I replied I could recover to whatever was there at 00:15 that day, because, with Crondsys we stop the database, then backup the entire Oracle directory and all of its subdirectories (I was told I actually only needed to keep the oradata folder but we have a large SAN so why not get all the stuff config file, etc) and an interface directory where daily interface files and archives are kept from a system that sends data to TPOCS via importable text delimited flat files.
I received a few concerned looks because the using departments were under the impression that I could bring them back to just before the failure. I can't and the vendor that was tasked to provide the database application was only tasked to provide a 24 hour backup scenario. If a site wants anything better they have to do it on their own after submitting the plan and procedures to the tier 3 helpdesk (the vendor) for approval.
I am doing a lot of reading right now, but I would like to get your ideas on the cost and complexity of getting a true PIT recovery system in place or can a near PIT be established like configuring the redo logs to reside on the SAN instead of the local server?
v/r
Stephen S. Wolfe, GS-11, DAFC
Data Services Manager
stephen.wolfe_at_macdill.af.mil
(813) 827-9972 DSN 651-9972=3D20
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlput 'unsubscribe' in the subject line.
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org
 |
 |