This is a bug within TSM that is supposed to be fixed in TSM 4.1.3 server
code. I have not upgraded to test this function yet.

Linda Seeba                               Phone: (314) 234-5190
I/T Specialist - Sr                      Fax: (314) 232-4581
IBM Global Services               E-Mail:seeba AT us.ibm DOT com

---------------------- Forwarded by Linda Seeba/St Louis/IBM on 04/10/2001
12:33 PM ---------------------------
12:33 PM ---------------------------

HK Chng <hkchng1 AT SINGNET.COM DOT SG>@VM.MARIST.EDU> on 04/10/2001 12:13:04 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:  Error in Backupset Expiration



Hi all, does anyone know of a way to delete backupset entires from
the database besides the delete backupset command ?

We had a problem this morning when our TSM Database backup failed
reason being that all the scratch tapes were not released from the
expiration of backupsets which shared the same scratch pool. The
backupsets had retention period of 7 days, however, since 28th March,
the expiration process was somehow not working. When I issued a query
backupset set, I see 7 generations from 4/4 - 10/4. However, when I
queried the volumehistory, it showed backupset entries from 3/28 -
4/10. As there was only 7 generations from the backupset query
result, I had no idea how to reclaim the rest of the cartridges. I
tried to force a re-labeling by using the overwrite=yes option, but
TSM wouldn't let the process complete successfully. As a temporary
bypass, I have switch the database backup & backupset generation to
using the private pool tapes instead. My environment is AIX 4.3.3,
TSM 3.7.4.0, 3494 tape library.

Would appreciate if anyone has any other ways of deleting the
obsolete entries fromthe database directly.


Regards.
Chng
Storage Administrator.