>>is that the case? tdp manages the inactivating of the prior full on the TSM >>side? so this can be related to be akin to similar to a file backup where >>once the file is deleted (or marked inactive by TDP) the backup falls under >>the 30 day expiration window. << With rman and TSM for DB (oracle), each backup "file" that TSM gets is a unique name. Therefore it is always "active" to TSM and TSM won't expire it. From the "Data Protection for Oracle for UNIX and Linux Installation and User’s Guide" manual: "RMAN uses the format parameter (in the RMAN script) to generate unique backup file names. Because all backup objects inserted into the Tivoli Storage Manager backup storage pool have unique file names, they never expire on the Tivoli Storage Manager server. As a result, Data Protection for Oracle requires these special Tivoli Storage Manager policy domain settings: Backup copy group values Data Protection for Oracle provides the tdposync utility to remove unwanted backup objects from the Tivoli Storage Manager server. It is recommended that the following Tivoli Storage Manager backup copy group options be set: v verdeleted 0 v retonly 0Then, when Data Protection for Oracle marks a backup object inactive, that object is deleted from the Tivoli Storage Manager server the next time expiration processing occurs. A backup object is marked for immediate expiration when you delete it through RMAN using the Data Protection for Oracle interface or with the tdposync utility. Note that an inactive backup object cannot be restored through RMAN using the Data Protection for Oracle interface. Notes: 1. The Tivoli Storage Manager administrator must also register your node by specifying backdelete yes in order for backup objects to be deleted. However, be aware that a backup object is marked for immediate expiration when backdelete yes and you delete it through RMAN using the Data Protection for Oracle interface or with the tdposync utility."
>>> js1000 <tsm-fo...@backupcentral.com> 4/6/2011 3:59 PM >>> The posting doesn't specify which TDP, which would help understanding. TDP for sql with a variety of different versions depending on which server Which means that to TSM they are all active backups and TSM will therefore not expire them. They have to be expired/deleted from the TDP side, e.g. rman for oracle. is that the case? tdp manages the inactivating of the prior full on the TSM side? so this can be related to be akin to similar to a file backup where once the file is deleted (or marked inactive by TDP) the backup falls under the 30 day expiration window. +---------------------------------------------------------------------- |This was sent by jonathan.s...@osumc.edu via Backup Central. |Forward SPAM to ab...@backupcentral.com. +----------------------------------------------------------------------
