ViPR 2.2 - Data Mobility: Change the ViPR Virtual Array in a VPLEX Environment
Table of Contents
- Move a VPLEX virtual volume from one VPLEX cluster to another.
- Reassign the VPLEX virtual volume's ViPR virtual array to a different virtual array.
- Change the back end physical storage volume on which VPLEX virtual volume is based to another physical storage volume assigned to the new virtual array.
- Move the data on the original physical storage volume to the new storage volume.
In previous versions of ViPR, Virtual Array Change operations could be performed on VPLEX virtual volumes, but no attempt was made to manage the consistency groups on the back end physical arrays.
In ViPR 2.2, if you use Change Virtual Array to change the physical backing storage for a VPLEX Local virtual volume, you must change the backing storage for all VPLEX virtual volumes that belong to the same VPLEX consistency group as the target volume.
Before you run the Change Virtual Array service, note the following:
- Virtual array changes are only allowed for uningested, unexported, local VPLEX volumes that have connectivity to the target virtual array.
- If you are migrating volumes that share a VPLEX consistency group created with ViPR 2.2 to another virtual array, the matched or assigned storage pools in the virtual pool of the target virtual array must be on the same physical storage system.
- If the user selects a volume in a consistency group, all volumes in the consistency group, and only the volumes in the consistency group must be selected. Otherwise, none of the selected volumes can be in a consistency group.
- For virtual array changes, the virtual pool for the volume does not change. The virtual pool for the volume must be valid for both the source and the target virtual array.
Before you begin
- This operation requires the System Administrator role in ViPR.
- This service is only supported on VPLEX local virtual volumes that have not been exported to a host.
- The new block storage volume is created from the same virtual pool as the original block storage volume. Therefore the new virtual array being chosen must be configured with the same virtual pool as the original virtual array that was used for the VPLEX virtual volume.
- A maximum of 25 volumes at a time can be moved from one virtual array into another. However, if the volumes are in a consistency group, there is no maximum volume limitation when moving volumes into a different virtual array.
- From the Service Catalog, run .
- Select the project to which the volume belongs.
- Select the volume or volumes to move. If you are moving a volume in a VPLEX consistency group, choose all the volumes in the VPLEX consistency group.
- Select the virtual array to which the volumes will be moved.
- Click Order.
- The VPLEX is configured with Cluster 1 on Virtual Array A, and Cluster 2 on Virtual Array Z.
- The back end storage for VPLEX Virtual Volume A, on Cluster 1 is configured from VMAX A.2, which is part of Virtual Array A.
In the next image the virtual array for VPLEX Virtual Volume A is changed to Virtual Array Z.
- A new back end storage volume, from the same virtual pool, is configured for VPLEX Virtual Volume A on VMAX Z.2 on Virtual Array Z.
- The data from the VMAX A.2 back end volume is migrated to the new back end volume on VMAX Z.2 using VPLEX local device migration, resulting in VPLEX Virtual Volume A being moved to Cluster 2 in Virtual Array Z.
- The VMAX A.2 back end volume is then unexported from VPLEX Cluster 1 and deleted.
Related ArticleBack to Top
- The VPLEX Local has three virtual volumes. The volumes are in a ViPR 2.2 consistency group.
- On the VPLEX , the three virtual volumes are in a VPLEX consistency group.
- The three virtual volumes have backing storage on VMAX1. The three physical volumes on VMAX1 are in a VMAX consistency group,
- The volumes have been moved to the Springfield virtual array.
- The backing storage volumes have been deleted from VMAX1.
- The volumes have been removed from the VMAX1 consistency group, and the VMAX1 consistency group has been deleted.
- The volumes are moved to VMAX2.
- A new consistency group is built on VMAX2. The three volumes are added to it.
For information on the VPLEX versions supported by ViPR 2.2, refer to the EMC ViPR Support Matrix.Back to Top