VLUN migration only migrates extents from one pool to another.  The Clariions would be able to do as you suggested though.  You're only choice to expand the device on the array is to temporarily form a concatenated meta then immediately convert it to a striped meta using a BCV to protect the data.  An alternative would be to use Powerpath Migration Enabler to migrate the volume to a new larger meta.  Neither option requires an outage of any kind.
Hello team,  VMAX 40K running 5876 code. I have a device of 128 GB thin device to be expanded to 512 GB, which is running SQL server.  Device is not any part of META. Have three pools 1) FC (RAID-5 3+1) 2) EFD (RAID-5 3+1) 3) SATA RAID 6(6+2) in total.  Device in question is part of FC (RAID-5 3+1). Standards are set in a way that does not allow use of concatenated meta at any stage due to performance issues had earlier. (SQL servers in prod envt)   1) If I create a new META in another Pool, does VLUN migration supports a " normal device to >> Meta" Migration ? 2) Device is part of a storage group which has got other many devices too. Would i be able to move data of only single device to a Larger device in another pool ? 3)At any moment do we need any down-time to perform VLUN migration from FC Pool to SATA pool ?  Can anybody give some insight on VLUN migration ?
Lun expansion from Non-META to a META