Hi Kenneth -  To answer you questions, 1] What is the impact of access to data in removing a Virtual Volume from a CG?      There is no impact to the virtual volume, the data can be copied non-disruptively  2] What are the impacts of replication and synchronization when removing a Virtual Volume from a CG?     There is no impact, the physical data relocation is preformed by VPLEX transparently and the virtual volume       retains the same identities and the same access points to the host. VPLEX copies the data from the old array       to the new array while the host continues its access to the virtual volume without disruption.  3] I presume that the volume(s) have to remain out of the CGs until the migration is completed, and then place back     into the CG?     Correct.  4] Any best practice/guidelines in doing this? ( destroy the consistency group. migrate all devices, then rebuild it?     or do one device at a time?)     Please refer to "VPLEX Data Mobility and Migration: Implementing Planning and Best Practices" which can be found     on Online Support, [URL] There is also some info in the VPLEX Administration Guide, also available on support online, look for the version for the code running on the VPLEX. And the CLI Guide will provide details of the commands to be used. There is also the procedure, "Migrate data from old array to new array" available from the SolVe Desktop procedure generator app, VPLEX > VPLEX Procedures > Administration procedures > Manage
We presently have a VPLEX Metro running and presenting storage to WSFC (Oracle cluster).  Runs great.  We are in a situation where we need to migrate the backend LUNs to another storage array, and wanted to leverage the capabilities of VPLEX to do so.  During research, I came to determine that any devices/extents being used in Consistency Group (CG, which we use) must be removed prior to such migrations.  So my questions...  1.) What is the impact of access to data in removing a Virtual Volume from a CG? 2.) What are the impacts of replication and synchronization when removing a Virtual Volume from a CG? 3.) I presume that the volume(s) have to remain out of the CG until the migration is completed, and then placed back into the CG? 4.) Any best practices/guidelines in doing this?  (destroy the consistency group, migrate all devices, then rebuild it?, or do one device at a time?)  Any insight would be most appreciative.
Migration of Consistency Group members?