You're on track Roger,   migration is triggered by lowering the threshold,
then resetting it to its original higher level (in my case 95%).   One
suggestion, don't lower it to 0%.  I did this to trigger migration and found
if a client is backing up when migration triggers, the migration never ended
until the client backup finished.   1% allowed the migration to finish, then
the client backup continued until finished.   Hope this helps you.

> ----------
> From:         Roger Hohmann[SMTP:roger_hohmann AT WESTLB DOT DE]
> Sent:         Friday, July 17, 1998 2:45 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Controlled migration
>
> We are using adsm v.3 with disk and tape storage pool. When our disk pool
> is nearly at high threshold and multiple backup schedules are starting,
> our
> disk pool likes to overflow because the migration processes can't move the
> data as fast as needed to tape. The backup and migration processes are
> interfering, backup becomes sloooow.
>
> I would like to empty my disk pools before backup starts. May I switch hi
> threshold to 0 to start migration and then switch back or should I use
> "move data"? Does anyone know? Any other ideas?
>
> Thanks in advance
> Roger Hohmann
>
> WestLB
> Tel.: +49211 826 8155
>