Re: rman restore from consistent backup

From: joel garry <joel-garry_at_home.com>
Date: Tue, 10 Feb 2009 10:35:40 -0800 (PST)
Message-ID: <b57c2414-0d37-4aa0-9ab8-79bbc3c4bd5b_at_z28g2000prd.googlegroups.com>



On Feb 10, 2:10 am, Charles Hooper <hooperc2..._at_yahoo.com> wrote:

> To the OP, a final note, which Sybrand among others have repeatedly
> stated (and I don't think too many people would want to disagree
> with), from "RMAN Recipes for Oracle Database 11g" Page 7:
> "If you are running a production database - or if you want to make
> sure all the data changes made to any database, for that matter, are
> always protected - you must operate your database in archivelog mode."
>

The second part, yes. The "If you are running a production database..." as stated with no context, no.

What is most important is to be explicit about what service level is expected. There are plenty of DW and DSS examples that are not transaction dependent, as well as more obscure distributive setups. For example, I've spit stuff out to various XE databases where all sorts of weird things can happen, no need to backup those at all. I find it common for users of ERP systems to be able to want to test or learn things, they only need restoration and perhaps recovery, logical backups if any. Is that production? Depends on their expectations.

For development databases described as production, it is just as important to be clear about SLA, and much more likely to go down in flames as a matter of course.

Just because the banner says "Production" doesn't mean the db needs archivelog mode. On the other hand, we still see silly people placing their eggs in a SAN basket. It all depends.

jg

--
_at_home.com is bogus.  "It may be strange for those not in the
networking field, but when things really go bad, the only place to be
is physically in the data center."
"Heh. I've heard that in the old day you could find broken Token ring
hardware by listening after a high pitched whining noise. Guess one
really has to be there for stuff like that."
"Was there, and confirm true. Whining noise normally came from IBM SE
who was trying to fix problem."
Slashdot slashdotted:  http://news.slashdot.org/article.pl?no_d2=1&sid=09/02/10/044221
Received on Tue Feb 10 2009 - 12:35:40 CST

Original text of this message