Yep, this tends to happen when you have only a small number of large clients
in a disk pool.

When the disk pool fills above the HIGHMIG value and triggers a migration,
TSM picks the LARGEST CLIENT (or maybe the largest filespace, I forget) in
the pool and migrates that WHOLE chunk out.  Then TSM checks to see it's
below LOWMIG yet.  If not, it picks the next largest client and migrates
that one.

So if all the remaining data in the disk pool belongs to one client, it can
go down to 0.

Working as designed.

-----Original Message-----
From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL AT SAIC DOT COM]
Sent: Tuesday, October 22, 2002 10:01 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Migrations


I have a disk pool that is set Migration Continue=no, High Migration=80, Low
Migration=60. This disk pool is 390GB in size and every morning when I come
in migration is running, and would run till it is empty, I've seen it. I've
verified the settings during the migration and I see no reason that this
should be happening. The disk fills with SAP R/3 data each evening and some
other regular stuff.

Has anyone else come across this? I haven't seen the other disk pools I have
do this.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:    <mailto:gillg AT saic DOT com> gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154