| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: rman restore & arclogs
I just
wanted to throw something else out there - it may have already come up
though. We backup the archivelogs first without deleting them, and then
immediately backup another set with the "delete" specified. Obviously,
this is because anything can happen to that first set (corruptions, etc.), and
if that's your only set, then you're screwed. The chances of the same
archivelog being corrupt in both sets is very low (unless the source archivelog
is corrupted), but at least you are protected against all the copy errors.
Also, it's very probable (for us, anyway) that each copy of the archivelog will
be on different physical tapes, which in itself is important to us since
operations is outsourced ; )
<FONT face=Arial color=#0000ff
size=2>
<FONT face=Arial color=#0000ff
size=2>Jim
<FONT face="Bookman Old Style"
size=2>__________________________________________________ <FONT face="Bookman Old Style" size=2>Jim Hawkins <FONTface="Bookman Old Style" size=2>Oracle Database Administrator <FONT face="Bookman Old Style" size=2>Data Management Center of Expertise Pharmacia Corporation <FONT
face="Bookman Old Style" size=2>800 North Lindbergh Blvd. <FONT face="Bookman Old Style" size=2>St. Louis, Missouri 63167 <FONT face="Bookman Old Style" size=2>Work (314)
size=2>Cellular (314) 724-9664 <FONT face="Bookman Old Style" size=2>Pager (314)
<FONT face=Tahoma
size=2>-----Original Message-----From: Mercadante, Thomas F
[mailto:NDATFM_at_labor.state.ny.us]Sent: Monday, December 03, 2001
12:56 PMTo: Multiple recipients of list ORACLE-LSubject:
RE: rman restore & arclogs
<SPAN
class=269064518-03122001>Lisa,
<SPAN
class=269064518-03122001>
I
guess I'm lazy (or cautious) in that I would allow the first backup to take
this archive log files back to tape where they belong, rather than determine
(by running reports) which log files I may delete (by
hand).
<SPAN
class=269064518-03122001>
The
cautious part of me says that if Rman decided to back these monkeys up within
the first save set after the recovery, it may have decided that it needs them
for a future recovery. If you did remove them by hand, Rman may complain
that it was expecting them and did not find them. Did you try this -
remove one that was restored by the recovery process and then tried a
backup?
<SPAN
class=269064518-03122001>
<SPAN
class=269064518-03122001>Depending on the kind of restore you do - a
full, or a point in time - the archivelog may be of no use anyway (a point in
time makes them invalid because you had to perform an "open db reset logs",
while a full restore could still use these again).
<SPAN
class=269064518-03122001>
Glad
you are at least experimenting with the tool before you put it in production -
it actually is fun to do a restore as it happens so
infrequently!
<SPAN
class=269064518-03122001>
Good
Luck!
Tom Mercadante <FONT face=Arial
size=2>Oracle Certified Professional
<FONT face=Tahoma
size=2>-----Original Message-----From: Koivu, Lisa
[mailto:lisa.koivu_at_efairfield.com]Sent: Monday, December 03, 2001
10:30 AMTo: Multiple recipients of list
ORACLE-LSubject: rman restore & arclogs
Good morning all -
I've been practicing rman restores. It's a lot
easier than I originally thought. I've noticed that when you restore
and the arclogs are needed, it restores them. Which is expected.
However, when I take another backup, these arclogs are included in the
backup set. This is unnecessary in my opinion and makes my backup
files larger than they need to be.
Is it standard practice to just delete the arclogs
that were already in a backup set prior to taking the immediate backup after
a recovery? I can verify what arclogs are where in the backup sets
with a report.
Any comments are appreciated. Thanks
Lisa Koivu Oracle
Database Monkey Fairfield Resorts, Inc.
954-935-4117
Received on Mon Dec 03 2001 - 14:17:40 CST
 |
 |