We have the same setup. TDPO backups go to separate nodes that have use their own pool. We have ongoing problems with RMAN deletes not changing the file in TSM (rman backup pieces) to inactive status, which are then removed during expiration. We don't know if it's RMAN, TDPO, or us with the problem. Our DBA's run TDPOSYNC fairly often to fix things up. Something is wrong and we just haven't had time to track it down. I have a script that queries the TSM backups table for files (rman backup pieces) that are older than our retension period. I run it once a week.
Rick "Gee, Norman" <norman....@lc.ca .GOV> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <ads...@vm.marist Subject .EDU> Re: TSM TDP Oracle - Expiration Opinions 03/20/2009 01:27 PM Please respond to "ADSM: Dist Stor Manager" <ads...@vm.marist .EDU> You will have to let RMAN do its job. Every RMAN backup piece and sets have unique file names and will never place a prior backup into an inactive status. How would you expire a RMAN backup since every backup piece is still active? Short of mass delete on filespace. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Friday, March 20, 2009 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: TSM TDP Oracle - Expiration Opinions We currently have your Oracle TDP Clients setup as a Separate node in separate a separate domain down to the storage pool hierarchy. That said we are having challenges with DBA's and their RMAN delete scripts for various reasons. According to the TDP for DB manual its recommended to have the RMAN catalog maintain retention which I would agree with but we are little success, and end up filling up virtual tape subsystems, orphaning data etc. The enough now is to have TSM maintain the RMAN retention and the DBA's would just clean their RMAN catalog with a crosscheck and delete process. What do you? Do you let RMAN maintain Retention or TSM maintain pitfalls of either? Best Regards, Charles Hart This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.