Hi Mike, I'm a bit late on this one *and* I may be stating the obvious, but from: > - Keep daily full backups for 1 week > - Keep full backups taken on Sunday for 1 month > - Keep 1 backup from every month for 1 year > - Keep all archive logs for 30 days is the monthly backup cold / off line? I guess so, if not you must keep all archived redos for that time, i.e. a year Sorry if that's already been discussed, but I thought better mention it than not. Cheers Tony ----- Original Message ----- From: "Roger Xu" <roger_xu@xxxxxxxxxxx> To: <vitalisman@xxxxxxxxx>; <mschmitt@xxxxxxxxxxxx> Cc: <oracle-l@xxxxxxxxxxxxx> Sent: Thursday, October 27, 2005 5:42 PM Subject: RE: RMAN Retention policies > I think as long as you keep the backup controlfile, you can always > restore your RMAN backup to another server. > You do not have to do cold backup, right? > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Vitalis Jerome > Sent: Saturday, October 22, 2005 2:57 AM > To: mschmitt@xxxxxxxxxxxx > Cc: oracle-l@xxxxxxxxxxxxx > Subject: Re: RMAN Retention policies > > Hi Mike, > > Yes, it is the way to go. > If these are cold backup, it will work flawlessly. > > Otherwise, I observed that the LOG parameter of the KEEP option was > buggy (our version was Oracle 9i, I can't remember the exact release): > while the docco said that LOG would keep the archived logs needed to > make the online backup consistent, in fact it kept *all* logs backed up > after the related backup. > So KEEP was not suitable for online backups. > > Regards, > Jerome > > On 10/21/05, Mike Schmitt <mschmitt@xxxxxxxxxxxx> wrote: > > > > Hi all, > > > > I was wondering if I could get some advice on the best way to handle > > retention policies as they relate to RMAN and media management > > software. This is for a mixed 9.2 and 10 environment. > > > > For example, if we wanted to implement a retention policy that looks > > like the following, and has all other backups removed from the tape > library. > > - Keep daily full backups for 1 week > > - Keep full backups taken on Sunday for 1 month > > - Keep 1 backup from every month for 1 year > > - Keep all archive logs for 30 days > > > > I am curious about what others do to handle this? Would it be best to > > > set a keep time for each backup that gets run, designating how long > > that particular backup should be retained, or would it be better to > > have a separate script log in and change the catalog to match what you > > > want the policy to look like. ( This is for TSM btw, and my > > impression is that TSM mainly leaves retention up to the commands it > > gets by way of TDP) > > > > I am currently leaning towards handling this with the keep option, but > > > I would appreciate any advice > > > > Thanks > > > > > > > > > > > > -- > > //www.freelists.org/webpage/oracle-l > > > -- > //www.freelists.org/webpage/oracle-l > > For technical support please email tech_support@xxxxxxxxxxx or you can > call (972)721-8257. > This email has been scanned for all viruses by the MessageLabs Email > Security System. > > > > This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material. > ____________________________________________________________________ > This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech_support@xxxxxxxxxxxx > -- > //www.freelists.org/webpage/oracle-l > > -- //www.freelists.org/webpage/oracle-l