Gill, Geoffrey L. wrote:
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
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 c
I suspect what is happening is that as you say the SAP "fills" the disk
pool. So when migration starts and after it gets below the
lowmig point, it will keep going bascially till it migrates the data
for
the current node's data it was working on when it hit the lowmig
point.
So if this was a large
