ViPR 2.2 - Data Mobility: Change the ViPR Virtual Pool in a VPLEX Environment
Table of Contents
Before you begin
This operation requires the System Administrator role in ViPR.
A maximum of 25 volumes at a time can be moved from one virtual pool into another. However, if the volumes are in a consistency group, there is no maximum volume limitation when moving volumes into a different virtual pool.
- Select Service Catalog.
- Select the project to which the volume belongs.
- Select the volume to be moved, or changed.
- Select the target virtual pool.
- Select Order.
Change virtual pool to create a new VPLEX virtual volume
Use the Change Virtual Pool service to import a block storage volume from ViPR to create a new VPLEX virtual volume.
- Storage volume B is on VMAX B array and part of Testing virtual pool.
- Metro mission critical virtual pool is associated with VPLEX A.
- Storage volume B, and VPLEX A, have no association.
- Storage volume B is then moved to the Metro Mission Critical virtual pool, which is associated to VPLEX A.
- VPLEX local virtual volume B is then created from the backend Storage volume B.
If creating a VPLEX distributed virtual volume from block storage, the VPLEX local virtual volume is created from the selected virtual pool. Then a new HA backend storage volume is created, and attached as a mirror to the VPLEX local virtual volume and the distributed VPLEX volume is created. The data from the backend storage for the VPLEX local virtual volume is then copied to the HA backend volume to ensure the two storage volumes are synchronized.
Change the VPLEX virtual volume remote protection
Use the Change Virtual Pools service to change the remote protection of a VPLEX virtual volume from local to distributed.
When the Virtual Pool in a VPLEX environment is changed from local to remote, a new HA backend storage volume is created, and attached as a mirror to the VPLEX local virtual volume. The data from the backend storage for the VPLEX local virtual volume is then copied to the HA backend volume to ensure the two storage volumes are synchronized.
In the initial setup, VPLEX (local) virtual volume A is associated with Local Mission Critical virtual pool. Its backend storage is volume A on VMAX array A.1 as demonstrated in the following figure.
- Backend (HA) volume Z is created in Virtual Array Z.
- The Backend (HA) volume Z in Virtual Array Z is attached as a mirror to the VPLEX virtual volume A in Virtual Array A , which changes the remote protection of VPLEX virtual volume A from a local to distributed.
Change the backend storage volume for a VPLEX virtual volume
Use the Change Virtual Pool service to change the backend storage of a VPLEX virtual volume to meet new configuration requirements such as storage system type, disk type, or protocols.
- Backend Storage volume B is created on VNX A, and associated with VPLEX virtual volume A.
- Storage volume A on VMAX A is deleted.
Related ArticleBack to Top
If the virtual volume you are moving is in a VPLEX consistency group:
- All VPLEX volumes in the consistency group must be selected for the virtual pool change.
- Only the volumes in the consistency group can be selected for the virtual pool change. Do not select other volumes.
- The storage pools in the target virtual pool, whether matched or manually assigned, must reside on a single storage system thereby ensuring the back end volumes will be placed on the same storage array, and as such, can be created in the same back end consistency group. For distributed volumes, the High Availability virtual pool in the target virtual pool has this same restriction.
- The target virtual pool must specify multi-volume consistency.
For information on the VPLEX versions supported by ViPR 2.2, refer to the EMC ViPR Support Matrix.Back to Top