Mark,

Also note:

A fixtest for the ADSMConnect Agent for Exchange which provides a
new command to delete old backup objects based on age is now available.
The fixtest can be found on the ftp/web server at:

http://index.storsys.ibm.com/adsm/fixtest/agents/ntexch/v1r1

   /ADSMAUTODELete:database (Where databasename can be a *)
   /IFOLDer:n               (Where all backups older than n are deleted)

File IC22589B.EXE contains the self-extracting install program.  This
fixtest includes the changes implemented in fixtest A.

The new command can be scheduled to provide automatic deletion of old
backup objects and thus can eliminate the need to use home grown scripts
for that purpose.  Detailed command syntax is provided in the readme file.

You will still need to consider the managament class implications
that are discussed in Chapter 2 of the Exchange Agent book (SH26-4071).

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com



"Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM> on 04/08/99 11:07:06 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Del Hoobler/Endicott/IBM)
Subject:  Exchange Agent Question





Hello All,
I have been using the Exchange Agent to backup my IS and DS for some time
now. I recently re-read the book and they state that you should create a
new
management class with a version deleted parameter set to 0. This was so
when
you delete the IS and or DS backup from the GUI it was actually deleted
from
the database and storage pools. When I first setup the Exchange Agent I
just
used the default management class for it's policy domain which had version
deleted set to 1 and retain last set to 365 days. Well I noticed by using
the SQL interface that I now have 106 copies of my DS and 99 copies of my
IS
in each of my three storage pools (primary, copy, and dr). It's totals
almost 600GB of stuff that I don't want. So what I did was change the
default mc to version deleted 0 and deleted the DS from the admin
interface.
Then I ran a expire inventory. After it was complete, much to my dismay,
the
106 copies of the DS were still there. They were not listed in the admin
interface anymore though but were still listed through a SQL Query. How can
I get rid of these extra copies?

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017
(212)716-2810