ActiveCluster vVols Requirements

User Guides for VMware Solutions
Audience
Public
Content Type
User Guides
Source Type
Documentation

Requirements

  • vCenter Server 8.0 U3 (Build 24022515) or later

  • ESXi 8.0 U3 (Build 24022510) or later

  • Purity//FA 6.6.11 or later (starting in Purity//FA 6.6.11 ActiveCluster + vVols is enabled by default)

    • While support for AC+vVols shipped in Purity//FA 6.6.8, a support case was required to enable the feature, as the feature was disabled by default. The required version was shifted to 6.6.11 and higher as this is the version that AC + vVols is enabled by default.

  • FlashArrays configured for Uniform Synchronous Replication

  • vSphere Environment has Uniform management path access to VASA Provider

  • Reviewing and implementing object limits and recommendations

FlashArray ActiveCluster vVols Object Limits

There are specific supported object limits for ActiveCluster and vVols. Please review the vVols Object Limits and filter by FlashArray Model and Purity//FA version as needed.

FlashArray Object Limits References

FlashArray object limits can vary model to model so please refer to the specific array model object limits to confirm that the number of allowed stretched pods, volumes and snapshots is considered and taken into account.

Here are the FlashArray model-specific object limits .

What is not supported with ActiveCluster vVols?

There are some configurations or workflows that are not supported to be used with stretched vVols storage containers.

  • Storage Containers not on container version 4 or higher can not be stretched

  • NVMe-vVols storage containers can not be stretched (nvme-vvols is not supported with vMSC at this time)

  • Non-Uniform configurations are not supported with vMSC with vVols (VMware limitation). VMware and Everpure are working to provide support for non-uniform configurations in a future release of both vSphere and Purity//FA.

  • Hosts that are connected to a stretched protocol endpoint can not have the host ports edited, removed or added

  • Stretched Storage Containers can not be unstretched at this time. This is a limitation of VMware and we are working with them to support this in a future release of vSphere and Purity//FA.

    • A storage vMotion will be required in order to migrate off a stretched container to an unstretched container.

  • Stretched Storage Containers must be private connections (only one vCenter has access). VMware will not support stretched containers that are shared.

  • Asynchronous replication from a stretched vVol datastore is supported, but the vVol Replication APIs to manage asynchronous failover to a third site from a stretched pod is not yet supported and will be added in a future Purity//FA release.

  • At this time Cloudsnap is not supported for use in pods in Purity//FA. This includes vVols pods or non-vVols pods. Which in turn means that Cloudsnap targets are not supported with vVols multiple storage containers or with ActiveCluster vVols.