We have a slightly differnt apprach for this .. 1. cp arch files to arch history location (stage 2 days worth achives on disk. there is a cron that fires everday and deletes all files from hostory arch location which are two or more days older)
2.there is a script that invokes rman to backup arch using delete input clause steps 1 and 2 are done every 4 hours for archives so that archives are backed up to tape and to ensure as per sla that we store atleast 2 days worth of archives on disk. at the end of the day take a db backup(full or inc as per sla. vaires from db to db) Deepak --- "HAWKINS, JAMES W [IT/1000]" <[EMAIL PROTECTED]> wrote: > 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 ; ) > > Jim > > > __________________________________________________ > Jim Hawkins > Oracle Database Administrator > Data Management Center of Expertise > > Pharmacia Corporation > 800 North Lindbergh Blvd. > St. Louis, Missouri 63167 > Work (314) 694-4417 > Cellular (314) 724-9664 > Pager (314) 294-9797 > > [EMAIL PROTECTED] > > -----Original Message----- > Sent: Monday, December 03, 2001 12:56 PM > To: Multiple recipients of list ORACLE-L > > > Lisa, > > 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). > > 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? > > 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). > > 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! > > Good Luck! > > Tom Mercadante > Oracle Certified Professional > > -----Original Message----- > Sent: Monday, December 03, 2001 10:30 AM > To: Multiple recipients of list ORACLE-L > > > > 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 > > __________________________________________________ Do You Yahoo!? Buy the perfect holiday gifts at Yahoo! Shopping. http://shopping.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Deepak Thapliyal INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- 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).
