I found it - thanks Del.

Del Hoobler wrote:

> Bill,
>
> Keep in mind..."deletion" in this case is really just forcing
> the object to an inactive state.  So, you need to
> take a closer look at the copygroup definitions.
> The TDP for SQL backups should have their own copygroup
> with VERDELETED set to 0.  That way, when expiration is run,
> any inactive backups will "really" be deleted.
>
> For more details, check the section titled:
>
>     "TSM Policy Requirements and Recommendations"
>
> in the TDP for SQL User's Guide.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM Corporation
> hoobler AT us.ibm DOT com
>
> William R Zehnder <wzehnder AT JCPENNEY DOT COM>@VM.MARIST.EDU> on 03/21/2000
> 12:23:25 PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject:  Autodelete of SQL backups
>
> I've got TDP (version 1.1.2) installed on an NT (4.0 sp5) client
> (version 3.7.1.03) with 50 SQL databases.  Its been backing up for
> several months and last week I noticed it was taking up nearly half a tb
> of tape space - actually closer to 400 gb's.  So I ran the autodelete
> command, successfully, and 2072 of 2373 objects were deleted.  When I
> check the node with the query occupancy command, it still shows all the
> versions exist.  Will I need to wait for the tapes that the deleted
> backups reside on get reclaimed, or is something else going on?  I ran
> the autodelete last Thursday and expiration and reclamation have run
> several times since then.
>
> My server version is 3.1.2.50.
>
> --
> Cordially,
>
> Bill Zehnder
> 972-431-8733  Fax 972-531-8733

--
Cordially,
Cordially,

Bill Zehnder
972-431-8733  Fax 972-531-8733