ViPR 2.2 - Data Mobility: Change the ViPR Virtual Pool in a VPLEX Environment

Table of Contents

About the Change Virtual Pool service

The ViPR service catalog includes a Change Virtual Pool service that allows you to fine tune your management of VPLEX virtual volumes in your data center. The Change Virtual Pool service allows data center administrators granular control of their data mobility requirements, including control of back end storage location and data protection.

Back to Top

How to change the ViPR virtual pool used in a VPLEX environment

The Change Virtual Pools service is located in the ViPR service catalog.

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.

Procedure

  1. Select Service Catalog> Block Storage Services > Change Virtual Pool.
  2. Select the project to which the volume belongs.
  3. Select the volume to be moved, or changed.
  4. Select the target virtual pool.
  5. Select Order.
Back to Top

Use cases for changing the ViPR virtual pool in a VPLEX environment

The Change Virtual Pool service supports three different functions for VPLEX. This section describes those use cases.

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.

If creating a VPLEX local virtual volume, an existing block storage volume, which is selected during the virtual pool change operation, is used for the backend storage used to create the VPLEX local virtual volume. In the following figure:

Storage volume B vrtual pool initial setup

  • 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.
The virtual pool for Storage volume B, is changed to Metro Mission Critical, which is a storage pool configured for VPLEX, as demonstrated in thenext figure:

Change virtual pool for Storage volume B

  • 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.

In the following figure, VPLEX virtual volume B is distributed, Backend volume Z is created in Virtual Array Z, and attached as a mirror to VPLEX virtual volume B:

Change virtual pool for Storage volume B in a distributed environment

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.

Initial environment set up with a virtual pool created for local protection

Once the virtual pool is changed for VPLEX (local) virtual volume A to Remote Mission Critical virtual pool, as demonstrated in the next figure:

Change to a virtual pool configured for remote protection

  • 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.

In the following figure VPLEX virtual volume A is associated with the VMAX virtual pool. The backend storage for VPLEX virtual volume A is Storage volume A on VMAX A array.

Initiall setup with VMAX virtual pool

When the virtual pool is changed to the VNX virtual pool, as demonstrated in the following figure:

Change to VNX virtual pool

  • 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 Article

Data Mobility: Change the ViPR Virtual Array in a VPLEX Environment

Back to Top

Change the back end storage for a VPLEX virtual volume in a consistency group

You can use the Change Virtual Pool service operation VPLEX Data Migration to move the backing storage for a VPLEX virtual volume from one physical array to another.

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.
Back to Top

Supported VPLEX Versions

For information on the VPLEX versions supported by ViPR 2.2, refer to the EMC ViPR Support Matrix.

Back to Top