Hi Grath,  There are two options for Migration and both works on the same method but at different levels unless its a Metro VPlex. Assuming yours is a Local, I would suggest doing a extent level migration/mobility since you will be swapping one leg of the Raid-1 at a time. This will avoid creating one more volume from the other array which will retire soon and all the cleanup work for that leg.  Hope this helps.  Thanks, Sathya
Hi,  I have a single engine VPLEX system presenting virtual volumes that are backed with a RAID-1 device with extents that goto LUNs on two seperate storage arrays. Both arrays are due for upgrade and will be swapped out one at a time. What is the recommended best practice in order to perform a non-disruptive migration - the VPLEX admin guide mentions:  The migration process inserts a temporary RAID 1 structure above the source device/extent with the target device/extent as an out-of-date leg of the RAID 1. The migration can be understood as the synchronization of the out-of-date leg (the target). After the migration is complete, the commit step detaches the source leg of the RAID 1, and removes the RAID 1.  The virtual volume, device, or extent is identical to the one before the migration except that the source device/extent is  replaced with the target device/extent.   Will this work even with an existing 'RAID-1' setup on the device? - so for example I will want to move an extent at a time (not both extents from both arrays) - so inessence will have a 3-way RAID-1 for the duration of the migration?  Thanks in advance for your advice and comments.  Garth
Using VPLEX for storage upgrade