No, I mean an incomplete recovery. In this case it is a time-based
incomplete recovery.

-----Original Message-----
Sent: Wednesday, October 23, 2002 12:39 PM
To: Multiple recipients of list ORACLE-L



Dont you mean complete recovery?

"You could then perform an incomplete recovery until 02:10:01 - 02:10:59 or
02:21:01 - 02:21:59, etc."




 

                    "Fink, Dan"

                    <Dan.Fink@mdx        To:     Multiple recipients of list
ORACLE-L <[EMAIL PROTECTED]>        
                    .com>                cc:

                    Sent by:             Subject:     RE: Opinions on B&R
scenarios                                 
                    root@fatcity.

                    com

 

 

                    October 23,

                    2002 02:11 PM

                    Please

                    respond to

                    ORACLE-L

 

 





It provides a window for an incomplete recovery during the time that the
backup is being performed.
For example
02:00 1st tablespace begins backup
04:00 last tablespace ends backup with no time gaps in between
It is not possible to perform an incomplete recovery from 02:00 to 04:00.

02:00 1st tablespace begins backup
02:10 1st tablespace ends backup
02:11 2nd tablespace begins backup
02:21 2nd tablespace ends backup
02:22 3rd tablespace begins backup
02:32 3rd tablespace ends backup
etc.

You could then perform an incomplete recovery until 02:10:01 - 02:10:59 or
02:21:01 - 02:21:59, etc.

Granted, it is not a common need to perform an incomplete recovery during
the time of a hot backup, but better safe than sorry.

Dan Fink

-----Original Message-----
Sent: Wednesday, October 23, 2002 11:20 AM
To: Multiple recipients of list ORACLE-L


On Wed, Oct 23, 2002 at 08:14:07AM -0800, Fink, Dan wrote:
> Rick,
>          I will assume that all logs are properly backed up.
>          The only difference in the recoverability of the 2 scenarios is
that
> an incomplete recovery cannot be done to a time while any tablespace in
the
> database is in hot backup mode. So, there is a window of exposure in
> Scenario 1, that does not exist in 2. For this reason, it is recommended
> that each tablespace be placed in backup mode, the files copied, the
> tablespace taken out of backup mode and the process sleeps for 1 minute.


1 minute?  What's that about?



> Repeat with the next tablespace, etc.
===============================================================


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Fink, Dan
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to