ADSM-L

Re: [ADSM-L] Shrinking scratch pools - tips?

2007-03-23 13:18:10
Subject: Re: [ADSM-L] Shrinking scratch pools - tips?
From: "Colwell, William F." <bcolwell AT DRAPER DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 23 Mar 2007 13:17:46 -0400
Chip,

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

I have also had a different kind of leak, where I have too many filling
tapes.
If you aren't collocating (!) then you should have only filling tapes
for as many migration task you run.  If collocating by node, then only
as many nodes and if by group only as many groups as you have.

I have seen - and I don't know why - every group in a server stops
writing to
the current filling tape and start another one.  

Thanks,

Bill Colwell
Draper Lab

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bell, Charles (Chip)
Sent: Friday, March 23, 2007 10:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Shrinking scratch pools - tips?

Since this a GREAT place for info, etc., I though I would ask for
tips/how-to's on tracking down why my scratch pools are dwindling, for
LTO/LTO2/VTL. My guess is I have a couple of clients that are sending
out a
vast amount of data to primary/copy. But without a good reporting tool,
how
can I tell? Expiration/reclamation runs fine, and I am going to run a
check
against my Iron Mountain inventory to see if there is anything there
that
should be here. What else would you guys/gals look at?  :-)  Thanks in
advance!

 

God bless you!!! 

Chip Bell 
Network Engineer I
IBM Tivoli Certified Deployment Professional 
Baptist Health System 
Birmingham, AL 



 



-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.