Re: [ADSM-L] Shrinking scratch pools - tips?
2007-03-23 16:07:55
I always use
Select volume_name from libvolumes where status='Private' and last_use is null
To get volumes that should be (maybe) scratch but aren't for some reason. Now
if you have a real private volume checked in that
hasn't been used yet, it will still show last_use as NULL. You need to check
that the tape is really scratch and then figure out
why/how it was made private. Like the tape doesn't have a label and you don't
have the library as autolabel...or the tape is
write-protected...
To find out if a tape is really a scratch, we usually run a select on the
volhistory and the last entry should be STGDELETE.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David Bronder
Sent: Friday, March 23, 2007 3:56 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Re: Shrinking scratch pools - tips?
Colwell, William F. wrote:
>
> I would check first for volume leaks. If this select returns anything
> it is bad -
>
> select volume_name from libvolumes where status = 'Private' and owner
> is null
That's not necessarily true. If you're using a standalone TSM server (not set
up as a library manager for other TSM servers), the
owner field in the libvolumes table can/will be null as well.
--
Hello World. David Bronder - Systems Admin
Segmentation Fault ITS-SPA, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm. david-bronder AT uiowa
DOT edu
|
|
|