Gary,

This is the copygroup definition:

VERE nol
VERD NOL
RETE 30
RETO 60

Yet we have backups from May '08.



        
        
ADSM-L AT VM.MARIST DOT EDU
________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Gary 
Bowers [gbowers AT ITRUS DOT COM]
Sent: Wednesday, October 07, 2009 8:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Expiration of Exchange

My guess is that you are mounting up the filesystem, and backing up
the files directly.  The log files in Exchange are probably getting a
new name as they are truncated, which means that there are no versions
of the files, only a single version that goes from active to inactive
when it is deleted from the server.  Check your "Retain Only"
parameter of the TSM Exchange Management class.  Make sure that this
is set to 30 days and not 365 or nolimit.  This should delete older
files, but only from the date they get marked inactive.

Gary
Itrus Technologies


On Oct 7, 2009, at 8:33 PM, Fred Johanson wrote:

> We use Copy Services instead of the TDP for EXCHANGE.  We want to
> keep backups for 30 days, which does work.  The .edb files are daily
> marked as inactive and roll off as expected.  But an examination by
> Mr. Exchange shows that there are .log files which are never marked
> as inactive, and, thus, are immortal, so far to the sum of 50 Tb on
> site (and the same offsite).  We obviously missed something in
> configuration, but what?
>
> To complicate matters, we tried to modify the client to allow
> deletion of backups (Mr. Exchange discovered on his own that "del ba
> *log todate=current_date-30" will get rid of the unwanted) but keep
> getting the client is accessing the server message, on an empty
> machine.  While waiting to figure this out, we could do "del vol xxx
> discarddat=y" on all those volumes more than 5 weeks old, but there
> must be some way to prevent this in the future.
>