Typically, you define a maximum size for the storage pool. The problem here is that the TDP is different and Oracle does not preannounce the object size. So, I think it will get to 20GB fail and then resend the object, but TDP for Oracle may not be able to resend, thus it will just fail. This is just a stab at what may happen. I have never seen it before.
-----Original Message----- From: Ike Hunley [mailto:[EMAIL PROTECTED]] Sent: Friday, March 29, 2002 7:47 PM To: [EMAIL PROTECTED] Subject: Re: Rman/TSm Question: When an object is passed via TDP to TSM for backup, does the defined storage pool in TSM have to have enough space to backup the entire object? If the storage pool has 20GB defined, but the object is 45GB, won't the backup spill over to the storage pool specified in the next storage pool? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Malbrough, Demetrius Sent: Thursday, March 28, 2002 4:23 PM To: [EMAIL PROTECTED] Subject: Re: Rman/TSm Mark, This is from the TDP for Oracle manual! RMAN generates unique backup file names. Because all backup objects inserted into the TSM backup storage pool have unique file names, they never expire on the TSM server. As a result, TDP for Oracle requires these special TSM policy domain settings: Backup Copy Group Values TDP for Oracle provides a delete function to remove unwanted backup objects from the TSM server. However, for the delete function to work, the following backup copy group parameters must be set: 6VERDELETED=0 6RETONLY=0 Then, when TDP for Oracle marks a backup object inactive, that object is deleted from the TSM server the next time expiration processing occurs. A backup object is marked inactive when you delete it through the TDP for Oracle interface. Notes: 1. The TSM administrator must also register your node by specifying BACKDELETE=YES in order for backup objects to be deleted. Regards, Demetrius Malbrough UNIX/TSM Administrator -----Original Message----- From: Mark Hayden [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 2:56 PM To: [EMAIL PROTECTED] Subject: Rman/TSm Hi all, we have a problem in regard to expiring data after Rman has deleted the data. We have taken the retention values down to 1 version with the RETONLY and VERDELETED to 0. When we do a select statement, they do show inactive, but are not expiring.....Do I have a TSM DB problem, or is there something else I'm missing???? Thanks for your help! Thanks, Mark Hayden Informations Systems Analyst E-Mail: [EMAIL PROTECTED]
