|Ingest Block Volumes
(Ingest Unmanaged Block Volumes into ViPR)
Supports the ingestion of block volumes from block storage systems that are managed by ViPR.
|| VMAX volumes that are not in existing masking views can be ingested. However, where masking views exist, the provisioning of standard or FAST LUNs can be affected. The following white paper describes the effects of masking views and zones.
VMAX and associated SRDF volumes.
|Supported for Synchronous volumes only.
A VPLEX volume not in storage view can be ingested. However, back end operations are not supported.
VNX volumes that are not exported to a host can be ingested.
ViPR does not support the ingestion of VNX volumes that are in a consistency group.
|Ingest File Systems
(Ingest Unmanaged File Systems into ViPR)
Supports the ingestion of file systems from file storage systems that are managed by ViPR.
||To be ingested by
ViPR a file system must have been exported.
When ingesting unmanaged file systems into
, there are a number of limitations on the handling of file system exports which will either cause the ingest operation to fail, or may impact the way exports are accessed. These are:
- An export can only have a single export rule.
- ViPR only supports exports with single security type. For example, an NFS export on an array is allowed to have multiple security types (sys, krb, krbi, krbp, etc.) while
ViPR only allows for one security type.
- All endpoints within an export have one set of host permissions (read-write, read-only and root) type.
- ViPR does not handle multiple use cases surrounding root user mappings.
|Ingest Object Data
(Ingest File System Data into ViPR Object Storage)
Supports the ingestion of object data from file systems that are managed by ViPR.
||When ingesting file systems into
ViPR object storage, the following limitations apply:
- The file system must be under ViPR management.
- The file system must not be exported. If it is, all exports must be removed.
|Import and move LUNs using Host Migration Utility
Can be used to onboard a non-ViPR LUN by migrating the data to a
Can change the virtual storage pool of a LUN by migrating a source LUN to a new target.
Documentation for this utility can be found here:
|Use Existing Masking Views
When creating VPLEX volumes, existing masking views provided they meet
criteria. The following White Paper discusses this scenario: