RE: backup best practices
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
- To: <swhite@xxxxxxxxxxxxx>, <Oracle-L@xxxxxxxxxxxxx>
- Date: Fri, 7 Oct 2005 10:50:35 -0400
Well, part of this will depend on whether you're running a "real"
O/S...;-) I'll let folks decide for themselves what a "real" O/S is or
is not....;-)
Seriously, though, in my opinion, a production database in archivelog
mode should almost never need to be bounced. I see no reason for
scheduled bounces or outages. Since 9i, when you can set SGA_MAX_SIZE
and dynamically adjust many, many parameters, there are fewer and fewer
reasons to need to bounce. A properly implemented hot backup strategy
should be able to provide for recovery from any type of media failure.
I can't think of any scenario where a cold backup is "better" than a hot
backup. I can't think of any reason to bounce a instance. All you do
is thrash the buffer cache and library cache.
My two cents,
-Mark
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Susan White
Sent: Friday, October 07, 2005 10:38 AM
To: 'Oracle-L@xxxxxxxxxxxxx'
Subject: backup best practices
Should off-line backups (RMAN or otherwise) be a part of a standard
backup strategy? In the "old" days, cold backups were recommended for
consistency - or at least that's how I understood it. Now, it seems that
these are not deemed essential. What is the recommended best practice
for off-line/on-line backups?
Related to this: Should the DB be "bounced" occasionally? In my last
oracle class, this was implied, although not stated. Any thoughts
Thanks
Susan White
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Other related posts:
