Yep.
I ran into the same thing with the TDP for Oracle.
Change the management class (copy group) from 2 to 0.
Next time expiration runs, it will all clean up.
> -----Original Message-----
> From: Phil Bone [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 11:51 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Really Dumb Mistake
>
> I would hope that it would be as simple as changing the Management Class
> and
> elevating the new policy. The next expiration should clean it up.
>
> Phil
>
> -----Original Message-----
> From: Palmadesso Jack [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 11:46 AM
> To: [EMAIL PROTECTED]
> Subject: Really Dumb Mistake
>
>
> We are using the ADSM connect agent with one of our exchange servers at a
> remote location. The level of the connect agent does not have the
> "autodelete" function to automatically remove older exchange objects. So
> what we need to do periodically is go into the exchange box and remove the
> last months backup objects manually. We've been doing this for 3 months
> but
> I was getting concerned when none of the tapes were being freed up by
> expiration and then reclaimed. It never concerned me too much because I
> knew the library had lots of space. Well after checking the management
> class for the exchange server I noticed that I had not set up some of the
> parameters correctly. Specifically "deleted objects" was set to 2 instead
> of the required 0. Of course this has the effect of keeping all objects
> because of the way exchange backups work.
>
> So now my dilemma is how do I get rid of what I don't want since its
> already
> been removed in the connect agent on the exchange box. Delete volume
> looks
> like my only option but it makes me a bit nervous because I'm not sure if
> it
> will cause any data continuity problems. Anybody have any advise for a
> dummy.
>
> ADSM Platform:
> AIX 4.1.5
> ADSM 3.1.40
> Exchange Server:
> NT4 sp5
> Exchange 5.5 sp3
>
> Thanks,
>
> Jack
