I do not understand the hard to manage argument, I use scripts to do all
of that sort of work.  It is nice to be able to fine tune the disk pool
sizes.  We have started resizing the pool volumes to reduce the threads
TSM uses, but it will take more than a week to complete.  It will take 2
days to do enough resizing to determine if this is the problem which is
why I asked the question.

It appears that our TSM servers can only handle about 2060 threads.
Does that sound right for an AIX server?

Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: Friday, January 06, 2006 3:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Primary disk pool volume limit

>> On Thu, 5 Jan 2006 22:29:26 -0600, Andy Huebner
<Andy.Huebner AT ALCONLABS DOT COM> said:

> Maybe I should have pointed out that this is not a theoretical
question.
> Are 1800 volumes too many?

I would say 'Hell yes!', but not from a technical-constraint
perspective;  I'd emphasize the management overhead involved in
keeping track of such things.

Strong suggestion:  during the times you _can_ get the server to keep
running, one-by-one

upd vol [foo] acc=reado
move data [foo]
del vol [foo]

Then remake the involved storage in a larger size.  Hopefully this
will get you under your pain threshold quickly, and then you can
gradually reform the rest.


- Allen S. Rout


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.