Hello all...

I have just discovered that Migration no longer worked the way it used to.  Once
upon a time I was able to set the storage pools high and low values to 0,
migration would start, then after maybe 20 seconds I would reset the values to
90 and 70.  Migration would continue to run until it reached the pre-set value
of 0, not 70.  Now when I run it, if I reset the values before it finishes, the
process assumes the new values and will end prematurely!

Have others found this to be true?  Is this by design or accident?  And lastly,
how do I automate the migration process if I need to watch it complete before I
can update the values?

Thanks for you input...

Scott