just use the TdP for Exchange client and delete 

via GUI 
or
with delete command you can schedule automatically

René Lambelet
Nestec S.A. / Informatique du Centre 
55, av. Nestlé  CH-1800 Vevey (Switzerland) 
*+41'21'924'35'43  7+41'21'924'28'88  * K4-117
email rene.lambelet AT nestle DOT com
Visit our site: http://www.nestle.com

        This message is intended only for the use of the addressee and 
        may contain information that is privileged and confidential.



> -----Original Message-----
> From: MC Matt Cooper (2838) [SMTP:Matt.Cooper AT AMGREETINGS DOT COM]
> Sent: Wednesday, August 15, 2001 1:55 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Expiring DB2 backups/what about ms-exchange?
> 
> Hello all,
>         I am having a similar looking problem but it involves MS-Exchange.
> I do not handle that client. But it sure would help if I can tell the NT
> administrators were to look to fix this problem.  Right now it looks like
> the MS-EXCHANGE backups stay forever with a date/time stamp as a file name
> and therefore stay ACTIVE.
> Matt
> 
> -----Original Message-----
> From: Gyula Bereczky [mailto:bx AT MAIL.DATATRANS DOT HU]
> Sent: Tuesday, August 14, 2001 8:35 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Expiring DB2 backups
> 
> On Wed, Aug 15, 2001 at 12:39:06AM +0200, Eduardo Martinez wrote:
> > As you know, when you backup DB2 it stamps an unique id to its backup,
> > making it an active version forever, then you can't expire that backup.
> > Does anyone know how to expire this kind of backups?
> 
> Use db2adutl's delete command to mark older versions for expiration.
> You can find the description of db2adutl in the db2 admin guide.
> 
> --
>        bx
> "Seize the day - I heard him say - life will not always be this way,
> Look around, hear the sounds, cherish your life while you're still
> around."