ADSM-L

Re: [ADSM-L] Expiration of Exchange

2009-10-08 17:07:00
Subject: Re: [ADSM-L] Expiration of Exchange
From: Fred Johanson <Fred AT UCHICAGO DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Oct 2009 16:04:52 -0500
Thanks Del,

Redfaced, I confess that I didn't extract the whole truth out of Mr. Exchange.  
This morning he admitted that he had used the same client name for testing the 
EXCHANGE TDP and never deleted his test files.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Del Hoobler
Sent: Thursday, October 08, 2009 6:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Expiration of Exchange

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.
>
>

<Prev in Thread] Current Thread [Next in Thread>