Been there, I don't know the proper way to fix it.
But here's a sneaky thing you can do if you have some free disk space:
Do another DBSNAPSHOT to DISK.
(You'll have to set up a FILE type DEVCLASS).
Then you will have 2 DBSNAPSHOTS, so you can delete the DBSNAPSHOT that is
on tape in your library.
Then use whatever operating system command to scratch the disk DBSNAPSHOT,
and free up your disk space.
You will be left with a bogus entry in your VOLHISTORY file, but at least
it's not taking up space...
-----Original Message-----
From: Joel Fuhrman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2001 2:39 AM
To: [EMAIL PROTECTED]
Subject: Re: removing last/only DBSnapshop
Unfortunately, the works for all but the last/only volume. In the output
from the TSM server command 'help del volh', it reads "The latest snapshot
database backup will not be deleted.".
On Mon, 4 Jun 2001, Mark Stapleton wrote:
> Joel Fuhrman wrote:
> > I did a snap shot database backup to see what impact, if any, it would
have
> > on the logfile. Unfortunately, I didn't realize that it is not possible
to
> > delete this backup using normal commands. I don't want a volume
containing
> > useless data in my library from now until TSM doomsday.
> >
> > Does anybody know of a back door method to remove the last/only
DBSnapshot
> > volume from the TSM database.
>
> I'm not sure who told you a DBS couldn't be deleted. No backdoor is
> necessary:
>
> del volhist begind=-3 type=dbs
>
> All database snapshots will be thus deleted if 1) they are at least 3
> days old, and 2) there is at least one other database backup (including
> full backups).
>
> --
> Mark Stapleton ([EMAIL PROTECTED])
>
