ViPR 2.1 - Using ViPR with Existing Environments

Table of Contents

Use ViPR with existing environments

ViPR enables storage arrays to be added to a virtual data center and for their storage pools to be used as the target for block, file, and object storage provisioning operations. Where storage pools already host block volumes, or file systems, that were created outside ViPR, and are not currently managed by ViPR, ViPR provides mechanisms for bringing them under ViPR management.

The mechanism for bringing storage under ViPR control is referred to as ingestion.

Where you are using ViPR object storage, file system data can be ingested into ViPR as object data and accessed using the supported object protocols or as a Hadoop Distributed File System (HDFS). ViPR also provides the ability to ingest volumes that are part of a VPLEX configuration, or that are protected using RecoverPoint (RP) or Symmetrix Remote Protection Facility (SRDF).

The way in which existing storage has been provisioned on an array affects the ability of ViPR to ingest block volumes or file systems from the array, and can affect future provisioning operations. The following table lists the import mechanisms that are provided and identifies any limitations.

Back to Top

Block storage systems under ViPR management

Once a volume is under ViPR management, and has been provisioned or exported to a host through a ViPR service, you should no longer use the storage system element manager to provision or export the volume to hosts. Using only ViPR to manage the volume will prevent conflicts between the storage system database and the ViPR database, as well as avoid concurrent lock operations being sent to the storage system. Some examples of failures that could occur when the element manager and ViPR database are not synchronized are:
  • If you use the element manager to create a volume, and at the same time another user tries to run the "Create a Volume" service from ViPR on the same storage system, the storage system may be locked by the operation run from the element manager, causing the ViPR “Create a Volume” operation to fail.
  • After a volume was exported to a host through ViPR, the same masking view, which was used by ViPR during the export, was changed on the storage system through the element manager. When ViPR attempts to use the masking view again, the operation will fails because what ViPR has in the database for the masking view is not the same as the actual masking view reconfigured on the storage system.
You can, however, continue to use the storage system element manager to manage storage pools, add capacity, and troubleshoot ViPR issues.

Back to Top

File storage systems under ViPR management

Once a filesystem is under ViPR management, and has been provisioned or exported to a host through a ViPR service, you should no longer use the storage system element manager to provision or export the filesystem to hosts. Using only ViPR to manage the volume will prevent conflicts between the storage system database and the ViPR database, as well as avoid concurrent lock operations being sent to the storage system. You can however continue to use the storage system element manager to manage storage pools, add capacity, and troubleshoot ViPR issues.

Back to Top