Ingest Unmanaged Block Volumes into ViPR

Table of Contents

Back to Top

Introduction

Existing block volumes can be brought under ViPR management by ingesting them using services provided in the Service Catalog. The operation is a two stage process and requires the use of two services, a discovery service followed by an ingestion service. The services are for use by System Administrators only and are not visible to normal catalog users. This articles describes how to use these services and provides additional information to support some ingestion use cases.

This article applies to EMC ViPR 2.0.

Once under ViPR management, ingested storage resources can be managed by provisioning users in the same way as if they had been created using ViPR, allowing them to be exported to hosts, expanded, protected using snapshot and copy techniques, etc.

Any volume that is brought under ViPR management must be assigned to a block virtual pool. So, before you can ingest volumes, you must ensure that a virtual pool exists whose criteria match those of the volumes to be ingested. For example, if you want to ingest volumes located on solid state devices (SSDs), you must ensure that virtual pools exists that allow SSDs. Similarly, if you want to ingest VMAX volumes that have associated SRDF volumes, you must ensure that there is a block virtual pool that can have VMAX volumes that are SRDF protected.

The discovery process finds volumes on a specified array and matches them with block virtual pools. When you use the ingest service, only volumes that were previously discovered to belong to a specified virtual pool are ingested.

Back to Top

Ingest block volumes from the ViPR UI

To ingest block volumes using the service catalog at the ViPR UI, the following operations must be performed.

Procedure

  1. Discover all unmanaged block volumes on an array.
  2. Ingest discovered block volumes.
Back to Top

Discover unmanaged volumes

The ViPR service catalog provides a Discover Unmanaged Volumes service that finds block volumes which are not under ViPR management. The operation is also supported from the ViPR API and CLI.

Before you begin

The following prerequisites are applicable:
  • This operation requires the System Administrator role in ViPR.

  • The virtual array and virtual pool into which you want to ingest the storage pools must exist when the discovery is performed.

    The discovery process finds storage pools on a selected storage system and identifies the virtual array and virtual pool that each array matches with.

Procedure

  1. Select User > Service Catalog > Block Storage Services > Discover Unmanaged Volumes.
  2. Select the physical block storage system on which you want to discover unmanaged volumes. You can select more than one storage system.
  3. Select Order.
    The orders page is displayed and shows the progress of the request. If the order is successfully fulfilled, you can use the Ingest Unmanaged Volumes to bring them under management by ViPR.
Back to Top

Ingest unmanaged volumes

The ViPR service catalog provides an Ingest Unmanaged Volumes Systems service that brings previously discovered unmanaged block volumes under ViPR management. The unmanged volumes must be in virtual pools associated with the virtual array from which to ingest. The operation is also supported from the ViPR API and CLI.

Before you begin

  • This operation requires the System Administrator role in ViPR.
  • To be ingested, the unmanged volumes must be in physical pools which are already associated with a ViPR virtual pool.

  • The Discover Unmanaged Volumes service must have been run on the array from which the block volumes will be ingested.

  • If the virtual array or virtual pool has been modified since the last time the unmanaged volumes were discovered, rerun the discovery prior to running the ingest operation to ensure volumes are assigned to the correct virtual array and virtual pool.
  • Ingested volumes will be assigned to a project. You must belong to the selected project and have write-permission on the project.

Procedure

  1. At the ViPR UI, switch to User mode at the and select Service Catalog > Block Storage Services > Ingest Unmanaged Volumes.
  2. Select the storage system from which you want to ingest block volumes.
  3. Select a virtual array that contains physical array storage pools that you want to import. The storage system might contribute physical storage pools to a number of virtual pools. If you want to ingest volumes that match other virtual pools you will need to run the service again for the other virtual pools.
  4. From the array physical storage pools that form part of the virtual array, select the virtual pool that the unmanged volumes are in.
  5. Select the project that you want the unmanaged volumes to be assigned to.
  6. Select Order.
    The orders page is displayed showing the progress of the request. If the order is successfully fulfilled, you can look at the User > Resources page to see the imported volumes.

After you finish

Once the unmanaged volumes have been ingested into ViPR, they can exported to a host and then mounted, or used for other functions such as SRDF mirror volumes.

To Export the volumes to either a Windows or Linux host using the following service, use:
  • User > Service Catalog > Block Storage Services > Export Volume to Host.

To mount the volumes on a host:
  • For Linux hosts use: User > Service Catalog > Block Service for Linux > Mount Existing Volume on Linux.
  • For Windows hosts use: User > Service Catalog > Block Service for Windows > Mount Existing Volume on Windows.

Back to Top

Block volume ingestion use cases

For some ingestion use cases, the ingestion procedure requires additional steps or additional information about the configuration required in order to perform ingestion.

Back to Top

Ingest SRDF protected volumes

Where you want to ingest VMAX volumes that are protected by SRDF, it is necessary to ingest both the source volume and the target volume. The source and target volumes must be ingested into different virtual pools. The source virtual pool must contain physical storage pools located on the source VMAX system, the target virtual pool must contain physical storage pools located on the target VMAX system. As the source and target volumes will be ingested into different virtual pools, you will need to perform two ingest operations.

It is assumed that you have two VMAX arrays and that SRDF protection between the arrays is configured. In addition, the two VMAX systems should be added to different ViPR virtual arrays. If you have not yet configured VMAX with SRDF you should follow the instructions provided in: Protect Data using VMAX SRDF Remote Replication with ViPR.

Note Image

It is possible for both source and target virtual pools to belong to the same virtual array, however, it is recommended that they are configured into different arrays to make the relationship clearer.

In performing the ingestion you must do the following:
  1. Ensure that you have set up a virtual array with a virtual pool that has SRDF protection configured. This virtual pool will be used to ingest the source volume. The virtual pool must specify Data Protection that uses the source virtual pool at the Admin > Virtual Assets > Block Virtual Pools page. The following settings should be specified:

    The virtual pool Data Protection panel with the appropriate selections is show below.

    SRDF protection on source virtual pool

    When Add Copy is selected, the target virtual array and virtual pool can be specified. Only virtual arrays and their constituent pools that can act as the target for the source VMAX are offered by this dialog.

    SRDF protection: specify target virtual pool

  2. Ensure that you have set up a virtual array with a virtual pool for ingesting the target volume. The virtual pool should not be SRDF protected.
  3. Run the discovery process and specify both the source and target VMAX arrays (Discover unmanaged volumes).
  4. After successful discovery on the source and target arrays, run the ingestion process on the source array followed by the target array (Ingest unmanaged volumes).
Back to Top

Ingest VPLEX volumes

Ingestion of VPLEX volumes can be achieved using the discover and ingest services from the ViPR service catalog, or using the ViPR API or CLI. Because ViPR does not support all of the array back end types supported by VPLEX, it can ingest the VPLEX virtual volume and perform operations that do not depend having control of the back-end array.

The following notes are applicable:
  • A volume can be ingested only if the VPLEX operations supported by ViPR can be performed. For example Export, Unexport, Mirror, Migrate etc.
  • A virtual volume can be ingested only if it not already exported (and if it does not have an local mirror attached).
  • Operations that require back end operations: Expand, Snap, Clone etc are not supported.
Ingested volumes can also be moved to a different virtual pool. This is useful where you want to migrate the back-end storage of a an ingested VPEX volume from an array that is not supported by ViPR to an array that is supported. When performing this virtual pool migration, the following apply:
  • A virtual pool change to migrate the back-end storage can be performed on all ingested Local VPLEX volumes. For distributed VPLEX volumes, the ingested volume must consist of a single extent on a single storage volume.
  • A virtual pool change of an ingested local VPLEX volume will result in a change to the name of the volume on the VPLEX. The VPLEX automatically changes the name of the local virtual volume to be the name of the local device on which it is built with the "_vol" suffix appended. Since it is migrated to a new local device created by ViPR, with the ViPR naming convention, the new name has the same convention as a ViPR created volume. This does not happen for a distributed volume, which uses VPLEX extent migration, because VPLEX device migration is not supported for distributed volumes.

A typical procedure for ingesting and moving an ingested volume is provided in: Move data from an unsupported array to supported array using VPLEX.

Back to Top

Move data from an unsupported array to supported array using VPLEX

You can use a VPLEX storage system managed by ViPR to move data from an array that is not supported by ViPR to a supported array. The procedure requires you to connect the unsupported array to VPLEX and ingest the source

Before you begin

  • Ensure that a VPLEX system has been added to ViPR and has been successfully discovered.
  • Ensure that a VPLEX virtual pool exists. This will be used to create a target volume to which data will be moved. The virtual pool must specify High Availability as VPLEX Local.
  • You must have the Tenant Administrator role in ViPR in order to access the Change Volume Virtual Pool Service.
  • You must have the System Administrator role to perform any physical or virtual asset operations and to run the discovery and ingestion services.

Procedure

  1. Connect VPLEX to the origin array.
  2. Encapsulate origin array volumes into VPLEX using the VPLEX UI or Unisphere.
  3. At the ViPR UI, create a virtual pool that includes the VPLEX physical storage pool that hosts the volume from which you want to ingest and migrate.
  4. In the UI user mode, run the discovery service User > Service Catalog > Block Storage Services > Discover Unmanaged Volumes on the VPLEX array.
    Details of running this service are provided in (Discover unmanaged volumes).
  5. After successful discovery, run the ingestion process (Ingest unmanaged volumes).
    You will need to specify the virtual pool that you created and that has the origin volume.
  6. If you have not already configured VPLEX to use the destination array, and configured a virtual pool that includes suitable storage pools from the destination array, you will need to:
    1. Bring the destination array online and connect it to the VPLEX array.
    2. Add the VPLEX array to ViPR and make sure that it has been discovered by ViPR.
    3. Create a virtual pool (in an existing or new virtual array) that includes the VPLEX virtual pool to which you want to migrate the data. The VPLEX virtual pool be a storage pool located on the destination backing array.
  7. Run the Change Volume Virtual Pool service to migrate the data. The service is located in the service catalog at User > Service Catalog > Block Storage Services > Change Volume Virtual Pool and specify the Operation as VPLEX Data Migration.
    More information on using the Change Volume Virtual Pool service can be found in: Change the ViPR Virtual Pool used in a VPLEX Environment
    This step will create volumes on both the VPLEX and the destination array and ViPR converts the underlying volume on the destination array to a ViPR-managed volume.
  8. At the ViPR UI, delete the origin volume using the User > Service Catalog > Block Storage Services > Remove Block Volumes service or using the Delete operation from the User > Resources > Volumes page. Specify the Deletion Type as Inventory Only.
    This will delete the volumes from ViPR only, the volumes remain on physical devices.
  9. The VPLEX and origin array can now be removed, if desired, since data is on the new array.

Results

Data from the unsupported array is now successfully migrated to the supported storage array.