From oracle-l-bounce@freelists.org Fri Oct 21 11:42:43 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j9LGgh5S018909 for ; Fri, 21 Oct 2005 11:42:43 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j9LGgevX018894 for ; Fri, 21 Oct 2005 11:42:40 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 968D620B36A; Fri, 21 Oct 2005 11:42:32 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21155-02; Fri, 21 Oct 2005 11:42:32 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 10EAC20B43C; Fri, 21 Oct 2005 11:42:32 -0500 (EST) Message-Id: <6.1.2.0.2.20051021111511.05e581c0@imap.uchicago.edu> X-Sender: mschmitt@imap.uchicago.edu Date: Fri, 21 Oct 2005 11:40:22 -0500 To: oracle-l@freelists.org From: Mike Schmitt Subject: RMAN Retention policies In-Reply-To: <83a585ac0510210900g1b3fddbejd135513c13c6362e@mail.gmail.co m> References: <83a585ac0510210900g1b3fddbejd135513c13c6362e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 27340 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: mschmitt@uchicago.edu Precedence: normal Reply-To: mschmitt@uchicago.edu X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Level: X-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 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 -- http://www.freelists.org/webpage/oracle-l