Ingest Unmanaged Block Volumes into ViPR
Table of Contents
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.
- Discover all unmanaged block volumes on an array.
- Ingest discovered block volumes.
Before you begin
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.
- Select .
- Select the physical block storage system on which you want to discover unmanaged volumes. You can select more than one storage system.
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.
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.
- At the ViPR UI, switch to User mode at the and select .
- Select the storage system from which you want to ingest block volumes.
- 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.
- From the array physical storage pools that form part of the virtual array, select the virtual pool that the unmanged volumes are in.
- Select the project that you want the unmanaged volumes to be assigned to.
The orders page is displayed showing the progress of the request. If the order is successfully fulfilled, you can look at thepage 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.
- For Linux hosts use: .
- For Windows hosts use: .
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.
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.
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 thepage. The following settings should be specified:
The virtual pool Data Protection panel with the appropriate selections is show below.
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.
- 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.
- Run the discovery process and specify both the source and target VMAX arrays (Discover unmanaged volumes).
- 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).
- 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.
- 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.
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.
- Connect VPLEX to the origin array.
- Encapsulate origin array volumes into VPLEX using the VPLEX UI or Unisphere.
- 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.
- In the UI user mode, run the discovery service
on the VPLEX array.
Details of running this service are provided in (Discover unmanaged volumes).
- 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.
- 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:
- Bring the destination array online and connect it to the VPLEX array.
- Add the VPLEX array to ViPR and make sure that it has been discovered by ViPR.
- 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.
- Run the Change Volume Virtual Pool service to migrate the data. The service is located in the service catalog at
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 EnvironmentThis 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.
- At the ViPR UI, delete the origin volume using the
Delete operation from the
page. Specify the Deletion Type as Inventory Only.
service or using the
This will delete the volumes from ViPR only, the volumes remain on physical devices.
- The VPLEX and origin array can now be removed, if desired, since data is on the new array.