RE: not including temp neither undo tablespace in full backup

  • From: "Mark W. Farnham" <mwf@xxxxxxxx>
  • To: <Mark.Bobak@xxxxxxxxxxxxxxx>, <juancarlosreyesp@xxxxxxxxx>, "Riyaj Shamsudeen" <rshamsud@xxxxxxxxxxxx>
  • Date: Thu, 13 Oct 2005 19:36:10 -0400

A fairly standard method is shutdown (some fast way, you pick it), startup
restrict, shutdown normal.

Now while this eliminates the "indefinite" waiting for everyone to log out,
it does not get you down quickly in the face of a very large rollback.

However, since every important situation I can recall put a high premium on
time to recover when a need to recover is detected, then if for some reason
you're relying on a cold backup, shouldn't it also be after a normal
shutdown so that the restart does not require an unknown length of rollback
before the database is fully operational? (I used to say operational at all,
but hooray you can open before all the rollbacks are complete in these
modern times.)

and the why bother? comment is pretty much on target.

only other bit I'd mention is to remember to get a copy of your current
on-line redo logs and control file as the first step of recovery. (not as
part of backup, unless that is a frozen complete set cold backup not
intended to ever be rolled forward).

mwf

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On
Behalf Of Bobak, Mark
Sent: Wednesday, October 12, 2005 3:57 PM
To: juancarlosreyesp@xxxxxxxxx; Riyaj Shamsudeen
Cc: oracle list
Subject: RE: not including temp neither undo tablespace in full backup

Hmm...a normal shutdown?  How long is that going to take?  (Has anyone
ever really used normal shutdown for anything useful?? ;-))

On any moderately busy database, you could be waiting indefinitely for a
normal shutdown.  (All it takes is one user to go home and not log out.)
you may be better off with a "shutdown transactional".

But, why bother?  Just follow the standard best practices, and don't
worry so much about your backups.  Always backup all datafiles, but
never tempfiles or on-line redo, and use the 'alter database backup
controlfile ...' command to make a backup copy of your controlfile.

-Mark
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Juan Carlos Reyes
Pacheco
Sent: Wednesday, October 12, 2005 3:42 PM
To: Riyaj Shamsudeen
Cc: oracle list
Subject: Re: not including temp neither undo tablespace in full backup

Thanks a lot Riyaj,
I had tested the situation you saidme in the past, but any way letme
test again.
Maybe I'll have to ask a normal shutdown.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l

Other related posts: