ADSM-L

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

2007-03-23 19:26:43
Subject: Re: [ADSM-L] Shrinking scratch pools - tips?
From: Sung Y Lee <sunglee AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 23 Mar 2007 19:24:24 -0400
Couple of things I would check.

Check each tape utilization.  Are they mostly 100%? or below 100%.
Do you have collocation turned on? If turned on, this would definitely
explain why taking up alot of tapes. Since each node gets it's own tape
volume.

Check retention?  many versions and longer retention period can cause alot
of tapes be used before expiration of data.

If the TSM server has been running for awhile, you should get an idea how
many tapes normally goes offsite  and how many tapes get reclaimed daily.
With this information it's easier to manage

Also are you checking in scratch tapes as used volumes are checked out?

Sung Y. Lee

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/23/2007
10:41:06 AM:

> 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.