both scenarios potentially lose the online redo logs. actually, since
you don't include the backup of the archived redo logs in either
scenario, you can't do recovery without a resetlogs for both scenarios.
In order not to lose the contents of the online logs, you have to
archive them and back
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
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
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
If the database crash causes media failure of your archive destination or
your online log destination, then you can only recover the database upto
the last archivelog availability, and you would need to open the database
with resetlogs. This is true for both scenarios.
Assuming no media
:
Sent by: Subject: RE: Opinions on BR scenarios
root@fatcity.
com
- 02:10:59 or
02:21:01 - 02:21:59, etc.
Fink, Dan
Dan.Fink@mdxTo: Multiple recipients of list
ORACLE-L [EMAIL PROTECTED]
.comcc:
Sent by: Subject: RE: Opinions
]
.comcc:
Sent by: Subject: RE: Opinions on BR scenarios
root@fatcity
Under this scenario, you have 2 options
1) Incomplete recovery to 2:10:30. Since there are no tablespaces in backup
mode, this is possible.
2) Do a complete recovery to the point of failure at 2:15:30. Of course, if
the failure was manual (oops, I dropped a table in production), then this is
not a
total sense.
next time I work without RMAN, I'll put in breaks in the backups.
--- Fink, Dan [EMAIL PROTECTED] wrote:
Under this scenario, you have 2 options
1) Incomplete recovery to 2:10:30. Since there are no tablespaces in
backup
mode, this is possible.
2) Do a complete recovery to the
How would i specify this sleep command in a 7.3/ebu/nbu configuration?
checking ebu docs..
-Original Message-
From: Fink, Dan [mailto:Dan.Fink;mdx.com]
Sent: Wednesday, October 23, 2002 3:09 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Opinions on BR scenarios
Under
11 matches
Mail list logo
