Yes, that is the setting I was refering to (badly). When I checked the
node error logs, I saw the messages about the setting being set to NO.

We just don't understand why occupancy for this node is 1/2 terrabyte when
the whole box only has 12GB used space ????

Oh well, back to digging for some answers !

Thanks for the help.





Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/20/2004 09:49 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Flushing out old TDP SQL backups


Zoltan,

Do you mean the TSM Server setting on the NODENAME
called "BACKDELETE=YES"? Even it is set to NO,
it will not keep your good backups from expiring.
The BACKDELETE=YES setting is only important for
cleaning up backups when there was a failure during
a backup and there are temporary objects left around
or if you are trying to change management classes.

If the backups were successful, the backups that exist
will follow the management classes that you have set up.
Once you have set BACKDELETE=YES, the next backup will
clean up any old temporary objects for any failed backups.

I don't think you have any "garbage" SQL backups.
If you do, I would need more details on why you think this.
You can also call IBM support, if necessary.

Thanks,

Del

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

> I goofed and forgot to set DELETE BACKUPS = YES on a TDP SQL client (now
> corrected)
>
>  So now, there are 1/2 Terrabyte of garbage SQL backups.
>
> How do I get rid of them ?
>
> I was hoping that EXPIRE INVENTORY would clear them out since I
corrected
> the setting, but it has not.