Skip to main content
VSC, VASA Provider, and SRA 9.7

Considerations for creating and editing storage capability profiles

Contributors netapp-asubhas
PDFs

You should be aware of the considerations for creating and editing storage capability profiles.

  • You can configure Min IOPS only on AFF systems.

  • You can configure QoS metrics at a virtual volume (VVol) datastore level.

    This capability provides greater flexibility in assigning varied QoS metrics for different VMDKs of the same virtual machine that is provisioned on a virtual datastore.

  • You can configure storage capability profiles for both FAS and AFF datastores.

    For FAS systems, you can configure space reserve to be either thick or thin, but for AFF systems, space reserve can only be configured to thin.

  • You can use storage capability profiles to provide encryption for your datastores.

  • You cannot modify existing storage capability profiles after upgrading from an earlier version of the virtual appliance for Virtual Storage Console (VSC), VASA Provider, and Storage Replication Adapter (SRA) to the latest version of the virtual appliance for VSC, VASA Provider, and SRA.

    The legacy storage capability profiles are retained for backward compatibility. If the default templates are not in use, then during the upgrade to the latest version of the virtual appliance for VSC, VASA Provider, and SRA, the existing templates are overridden to reflect the new QoS metrics related to the performance of the storage capability profiles.

  • You cannot modify or use the legacy storage capability profiles to provision new virtual datastores or VM storage policies.

  • You must use new storage capability profiles for all new datastores.