what does a 'q content vol_number' show?
running a 'move data' against the volume/tape should (if the tape is local
and not offsite) move the data off and then delete the tape from the storage
pool back to scratch status...?




Ted W. Qualls
PepsiCo Business Solutions Group
Systems Engineer - UNIX Engineering
5080 Spectrum Drive Suite 600W
Addison, TX 75001
office    972.376.7809
pager    972.297.6973
ted.w.qualls AT fritolay DOT com



-----Original Message-----
From: Mark Stapleton [mailto:stapleto AT BERBEE DOT COM]
Sent: Monday, September 16, 2002 12:10 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Deleting Backupsets - Recovering the tapes


From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Coats, Jack
> When I do a 'q libv' my listing shows two tapes
>
> LB6.0.0.1        175ACBL1        Private                   BackupSet 4,111
> LB6.0.0.1        191ACBL1        Private                   BackupSet 4,107
>
> I use the GUI to delete any existing backup sets, and it says there are
> none.  It generated the following messages:
>
> 09/16/2002 10:31:00   ANR2017I Administrator ADMIN issued command: DELETE
>                        BACKUPSET * * BEGINDATE=01/01/2001 BEGINTIME=NOW
>                        ENDDATE=09/16/2002 ENDTIME=NOW PREVIEW=NO
> 09/16/2002 10:31:56   ANR2034E DELETE BACKUPSET: No match found using this
                        criteria.
>
> How can I get these back into my scratch pool?
> How could I find out what is on each of these tapes (what backup set)?
>
> Currently when I do a Q BACKUPSET I get
> ANR2034E QUERY BACKUPSET: No match found using this criteria.
> message.

Try this (undocumented) command:

        q volh type=backupset

If you get entries from this, and the TSM server was upgraded from an
earlier version, you're pretty much in the same boat as one of my customers
was.

There is an (undocumented) way to get rid of the buggers:

        del volh type=backupset todate=<date_of_backupset_creation>
            volume=<volume_name> force=yes

WARNING WARNING WARNING
This command is undocumented, and if it causes problems, there is no support
for having used it.

--
Mark Stapleton (stapleton AT berbee DOT com)
Certified TSM consultant
Certified AIX system engineer
MCSE