Normally if the volume isn't register anywhere in TSM except that "q
libvol" is showing as last used backupset, you should be able to reset the
volume with the command "upd libvol LIBRARY_NAME VOLUME_NAME
status=scratch". At least this have worked a few times for me when TSM are
reporting tapes as last used dbbackup, even if the database backup process
failed.

Regards,
Odd-Magne

On Thu, 24 Apr 2003 14:00:16 -0500, Mark Bertrand
<Mark.Bertrand AT USUNWIRED DOT COM> wrote:

During creation of a backupset my TSM server crashed and rebooted (Bad
Processor). Now I have a tape volume that is showing up in q volhist as
last
used backupset. The backupset never had a chance to complete. I have
tried
to "delete vol VOLUMENAME discarddata=yes" but the volume does not
defined
in any storage pool.

In the old days we used to use "delete volhist type=backupset todate=(the
day after the backupset was created) totime=(the same time)
volume=(volumename in all CAPS) force=yes" to clear volumes that had
passed
the backupset retention setting to be able to reuse the tapes. When I
tried
the command I got "ANR2023E DELETE VOLHISTORY: Extraneous parameter -
volume."
Reading the help delete volhist it says " Use the DELETE BACKUPSET
command
to delete specified backup set volume information in the volume history
file. Do not use this DELETE VOLHISTORY command to delete backup set
volume
information in the volume history file."
I can not use the delete backupset command because the backup_set_name is
(Required), which I do not have because the create backupset never got
that
far.
I know I have an unusual situation because of the crash, but I was hoping
someone may have a suggestion.

TSM Server 5.1.6.3 Win2K
Thanks,
Mark Bertrand