Gerd,

There is no "delete" function for DP/Exchange backups.
A DP/Exhannge backup is made up of multiple TSM Server objects,
so I would not advise just deleting objects without making sure
you are deleting the entire "logical" backup... and even then
be very careful you are deleting the correct ones.
You should call IBM support if this is an urgent situation.
If you can wait until they expire, do that. If it is an
active backup, you can use the INACTIVATE command to
force an active backup to go inactive.
Here is the syntax for the INACTIVATE command:

TDPEXCC INACTivate *|sgname1,..,sgnameN backuptype
  where backuptype can be:
      FULL|COPY|INCRemental|DIFFerential|DBCopy dbname
  [/BACKUPDESTination=TSM|LOCAL]    (default: TSM)
  [/BACKUPMETHod=LEGACY|VSS]    (default: LEGACY)
  [/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)
  [/FROMEXCSERVer=servername] (default: local exchange server)
  [/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)
  [/LOGPrune=60|n|No] (default: 60)
  [/OBJect=object] (default: current active object)
  [/Quiet]
  [/TSMNODe=nodename]
  [/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)
  [/TSMPassword=password]

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/22/2007
05:21:15 AM:

> Hi *SM'ers,
> is there a supported way to delete obsolete backups from a filespace,
where
> erroneously versions are created. We did our yearly backup in the same
> Management Class, where the daily backups goes to. We changed out
> definitions in the way, it is described in the Technote swg21194253, but
> the superfluous versions still exist and needs space on the tapes. Now
we
> will delete these objects. One way is to find out the object id and
delete
> it with delete object, but this is the dangerous way and not supported.
Has
> anyone a better solution for me?
> Thanks
> Gerd W. Becker, Emprise