ViPR 2.1 - Configuration Considerations While Virtualizing Your Storage in ViPR

Table of Contents

Overview

ViPR System Administrators can review the information that should be considered while configuring specific types of storage systems in ViPRvirtual arrays and virtual pools, and understand how ViPR works with the storage system element managers once the volumes or file systems are under ViPR management.

For details about how you can create virtual arrays, and virtual pools see the following articles:

Back to Top

Block storage configuration considerations

Before you create virtual arrays and virtual pools for block storage in ViPR, review the following sections for storage system specific configuration requirements and recommendations:

Back to Top

VMAX

Review the following configuration requirements, and recommendations before virtualizing your VMAX system in ViPR.

Virtual Pool configuration requirements and recommendations

When VMAX is configured with Storage Tiers and FAST Policies:

  • Storage Tier and FAST Policy names must be consistent across all VMAX storage systems.
  • When configuring virtual pools in ViPR you will have to set the following options:
    Option Description
    RAID Level Select which RAID levels the volumes in the virtual pool will consist of.
    Unique Auto-tiering Policy Names When enabled, the unique auto-tiering names appear in the Auto-tiering policy selection list.

    When disabled, the general auto-tiering names appear in the Auto-tiering Policy selection list.

    Auto-tiering Policy The Fully Automated Storage Tiering (FAST) policy when VMAX System Type is selected.

    If a FAST policy is selected, ViPR will only use the FAST policy to display matching storage pools, regardless of the Drive Type and RAID Level selected when choosing matching storage pools.

    Example: Virtual pool is created with these parameters: Auto-tiering Policy: GOLD, Drive Type: Serial ATA, RAID Level: RAID1. Matching pools displayed show all storage pools that satisfy the GOLD FAST policy (could be storage pools that have FC and SSD drive types, not just Serial ATA). During provisioning, ViPR picks the Serial ATA (RAID1) pool as the Initial Placement Tier.

    FAST Expansion Enable for expansion to perform more quickly, however may cause performance issues.

Back to Top

EMC VNX for Block

Review the following configuration consideration before adding VNX for Block storage to the ViPR virtual pools.

Virtual pool configuration considerations

Fibre Channel networks for VNX for Block storage systems require an SP-A and SP-B port pair in each network, otherwise virtual pools cannot be created for the VNX for Block storage system.

Back to Top

EMC VPLEX

Review the following configuration requirements, and recommendations before virtualizing your third-party block storage in VPLEX .

Virtual array configuration requirements and recommendations

While creating virtual arrays, manually assign the VPLEX front-end and back-end ports of the cluster (1 or 2) to a virtual array, so that each VPLEX cluster is in its own ViPR virtual array.

Virtual pool configuration requirements and recommendations

When running VPLEX with VMAX, the Storage Tier and FAST Policy names must be consistent across all VMAX storage systems.

Back to Top

Third-party block (OpenStack) storage systems

Review the following configuration requirements, and recommendations before virtualizing your third-party block storage in ViPR.

Virtual pool recommendations and requirements

The first time you configure multipathing on the storage pools, set the fields as follows.
  • Max paths = 1
  • Min paths = 1
  • Paths per initiator = 1

If the discovered storage system is configured for multipathing, the values set in the virtual pool can be increased once the target ports are detected by ViPR.

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 configuration considerations

Review the following information before you add file storage systems to ViPRvirtual arrays and virtual pools, and before you use the file systems in a ViPR service.

Virtual pool for file storage configuration settings

File systems are only thinly provisioned. You must set the virtual pool to Thin, when adding file storage to the virtual pool.

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