It sounds a lot like TSM is allocating space in your disk pool for a lot
of data from many clients and finding itself maxed out.  It is not
always how much data is actually on the media, but how much space TSM
has allocated per client.

- Have you considered setting up larger clients to go directly to
Virtual Tape?  If you want data to go to VTL right away, send it there.
If you have 30 VTL drives, find the 10 or 15 clients with the biggest
sized files put them in a domain with a default management class that
points directly to VTL...or edit the include statements of the clients
(any client)to point the biggest files to a Virtual Tape management
class.  The second way does not require a new domain, but it requires
more work with clients.)
- I would also raise your threshold a bit so that you are not
continually in migration.

George Huebschman
Media Librarian
Legg Mason


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Loon, EJ van - SPLXM
Sent: Monday, October 05, 2009 4:47 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Migration problem

Hi Remco!
The high treshold is set to 5 because we want the data to go to virtual
tape a.s.a.p. This weekend the diskpool went to 100% again because of
the strange migration behavoir. The pool contained data from 100+
clients, but still no more than 2 migrations were running....
The tape deviceclass has mountlimit=drives which is 30 drives.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Remco Post
Sent: vrijdag 2 oktober 2009 17:10
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migration problem

Have you ever considered increasing the high threshold? IIRC TSM won't
start new automig processes when migration is already running, and will
only start as many processes as there are different clients having data
in your pool. Also, check out your mountlimit on the tape devclass.....

Furthermore, your disk pool might not be fast enough to keep your drives
streaming.

--
Met vriendelijke groeten,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only. If
you are not the addressee, you are notified that no part of the e-mail
or any attachment may be disclosed, copied or distributed, and that any
other action related to this e-mail or attachment is strictly
prohibited, and may be unlawful. If you have received this e-mail by
error, please notify the sender immediately by return e-mail, and delete
this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
its employees shall not be liable for the incorrect or incomplete
transmission of this e-mail or any attachments, nor responsible for any
delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered
number 33014286
**********************************************************************

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.