RE: rman restore & arclogs
Title: RE: rman restore & arclogs Lisa, I believe Oracle tries to restore the most recent version of the archivelogs, according to the timestamp in the catalog. But if that's corrupted or not found for whatever reason, you can get it from the other backupset. Jim P.S. Sorry for the vague answer, but I haven't ever had to do this so I'm not sure myself. I can ask our RMAN Guru if you really want to know ; ) __ 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-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]Sent: Monday, December 03, 2001 2:46 PMTo: '[EMAIL PROTECTED]'; HAWKINS, JAMES W [IT/1000]Subject: RE: rman restore & arclogs Interesting. Does rman ever get confused during a restore or does it just grab the most convenient backup set with the required archive logs on it? I don't suppose you can parallel restore your arclogs from different files/tapes? (There goes that monkey again) Thanks for your response Jim. Lisa -Original Message- From: HAWKINS, JAMES W [IT/1000] [SMTP:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 2:51 PM To: Multiple recipients of list ORACLE-L Subject: 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 ; ) Jim __Jim HawkinsOracle Database AdministratorData Management Center of Expertise Pharmacia Corporation800 North Lindbergh Blvd.St. Louis, Missouri 63167Work (314) 694-4417Cellular (314) 724-9664Pager (314) 294-9797 [EMAIL PROTECTED] -Original Message-From: Mercadante, Thomas F [mailto:[EMAIL PROTECTED]]Sent: Monday, December 03, 2001 12:56 PMTo: Multiple recipients of list ORACLE-LSubject: RE: rman restore & arclogsLisa, 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 MercadanteOracle Certified Professional -Original Message-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]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
RE: rman restore & arclogs
> being a dba is kinda fun. Once I actually got to start doing it, that is. Look Lisa, you keep that to yourself. Under no circumstances should you *ever* let a manager hear you say that. JARed "Koivu, Lisa" field.com> cc: Sent by: Subject: RE: rman restore & arclogs [EMAIL PROTECTED] 12/03/01 11:31 AM Please respond to ORACLE-L Thanks Tom. I did try removing the arclogs and then running a backup - no complaints. The arclogs in question were still present in the catalog via past backups. I'm guessing this is because the last scn of the last backup was larger than the scn's included in the arclogs in question. However, a crosscheck report caused failure for all those logs. Not a big deal, but once this all goes into production I want to see all my reports & lists sent to me every day with no "FAILURE" or anything of that nature in it. Erring conservative is probably better anyway, unless i'm really tight on disk. Restoring is kinda fun :) I take that back, being a dba is kinda fun. Once I actually got to start doing it, that is. -Original Message- From: Mercadante, Thomas F [SMTP:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 1:56 PM To: Multiple recipients of list ORACLE-L Subject:RE: rman restore & arclogs 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- From: Koivu, Lisa [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 10:30 AM To: Multiple recipients of list ORACLE-L Subject: 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 Re
RE: rman restore & arclogs
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).
RE: rman restore & arclogs
Title: RE: rman restore & arclogs Interesting. Does rman ever get confused during a restore or does it just grab the most convenient backup set with the required archive logs on it? I don't suppose you can parallel restore your arclogs from different files/tapes? (There goes that monkey again) Thanks for your response Jim. Lisa -Original Message- From: HAWKINS, JAMES W [IT/1000] [SMTP:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 2:51 PM To: Multiple recipients of list ORACLE-L Subject: 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 ; ) 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- From: Mercadante, Thomas F [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 12:56 PM To: Multiple recipients of list ORACLE-L Subject: RE: rman restore & arclogs 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- From: Koivu, Lisa [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 10:30 AM To: Multiple recipients of list ORACLE-L Subject: 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
RE: rman restore & arclogs
Title: 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 ; ) 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-From: Mercadante, Thomas F [mailto:[EMAIL PROTECTED]]Sent: Monday, December 03, 2001 12:56 PMTo: Multiple recipients of list ORACLE-LSubject: RE: rman restore & arclogs 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-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]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
RE: rman restore & arclogs
Title: RE: rman restore & arclogs Thanks Tom. I did try removing the arclogs and then running a backup - no complaints. The arclogs in question were still present in the catalog via past backups. I'm guessing this is because the last scn of the last backup was larger than the scn's included in the arclogs in question. However, a crosscheck report caused failure for all those logs. Not a big deal, but once this all goes into production I want to see all my reports & lists sent to me every day with no "FAILURE" or anything of that nature in it. Erring conservative is probably better anyway, unless i'm really tight on disk. Restoring is kinda fun :) I take that back, being a dba is kinda fun. Once I actually got to start doing it, that is. -Original Message- From: Mercadante, Thomas F [SMTP:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 1:56 PM To: Multiple recipients of list ORACLE-L Subject: RE: rman restore & arclogs 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- From: Koivu, Lisa [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 10:30 AM To: Multiple recipients of list ORACLE-L Subject: 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
RE: rman restore & arclogs
Title: rman restore & arclogs 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-From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]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
Re: rman restore & arclogs
Lisa, We backup all archivlogs with the backup set and delete them. Delete is an rman option when you backup archivelogs. We don't have room to keep them. It is a bit of a pain to restore them but you learn to live with it. Have a look at rman's tables and views. You should be able to query them and get what you want. Yours in rman, Ruth - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Monday, December 03, 2001 10:30 AM > 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 > > -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ruth Gramolini 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).
