Hi Fred,

All files backed up in an Exchange VSS backup are part of a "group".
The files in a "group" are all managed together. That means they expire
together
according to the management class of the "group" leader.

And so... I think something else is going on here. In fact, Gary probably
called it right when he said that maybe your normal file-level backup
client
is backing up these files.

If you cannot figure this out, you should call IBM support.

Thanks,

Del

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


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/07/2009
09:33:19 PM:

> [image removed]
>
> Expiration of Exchange
>
> Fred Johanson
>
> to:
>
> ADSM-L
>
> 10/07/2009 09:34 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> 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.
>
>