It gets even better, once a backupset has been deleted, even if you do a
"delete volhist tod=today t=all"
it still will NOT get rid of the backupset entry in the volhist :-(
as a matter of fact, I can't get rid of this dang backupset tape no matter
what I try !
I'm at 3.7.2.0 for AIX...
If I figure out anything I'll pass it along...
Dwight
-----Original Message-----
From: Cook, Dwight E
Sent: Tuesday, April 10, 2001 12:47 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: Error in Backupset Expiration
Oh, this is a HOOT !
you may do a "q volhist t=backupset"
but you may NOT do a "del volhist t=backupset ..."
you can see'em but you can't delete'em !
(unless you purge everything...)
Dwight
-----Original Message-----
From: HK Chng [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 12:13 PM
To: [EMAIL PROTECTED]
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.
