vSAN Metering and Reporting #
vSAN is activated at a host-cluster level either while creating new clusters or updating existing host clusters. vSAN aggregates all local storage devices across all hosts in the vSAN cluster into a single datastore. More storage devices or hosts can be added to the cluster to expand its datastore capacity. If a host contributes to the vSAN datastore, it must provide at least one device for flash cache and another for persistent storage. Capacity devices are also called data disks. The devices on the contributing hosts form one or more disk groups, and each disk group contains one flash cache device and one or more capacity devices. Devices used for caching cannot be shared across disk groups. Each host can be configured to use multiple disk groups. The amount of physical capacity from the vSAN datastore consumed by one or more VMs at any point is called the consumed capacity.
With Usage Meter 126.96.36.199, vSAN is automatically detected. There should be at least one vSAN cluster per vCenter Server so that Usage Meter detects and meters it. When one or more clusters in the vCenter are enabled with vSAN, the vCenter product configuration list page in the Usage Meter web application indicates that vSAN is associated and used for that vCenter.
Feature Detection #
vSAN usage is metered per vSAN enabled cluster (see Cluster History Report) and reported aggregated by vSAN license editions (see Monthly Usage Report). vSAN usage is collected on an hourly basis by the Usage Meter appliance. vSAN usage collection intervals are closed when one or more of the following scenarios occur:
- vSAN collection fails to send collected data for 24 hours or more
- vSAN enabled cluster is deleted
- vSAN license has changed
- When vCenter product is not metered and/or deleted from the Usage Meter web app Products page.
Note: The collection intervals are shown in the vSAN Cluster History Report.Specific space efficiency and QoS features are detected during these hourly collections and are used to determine the billing rate of vSAN usage.
vSAN usage is metered at a cluster level. While there are many features and capabilities that vSAN offers, from the perspective of usage metering, Usage Meter 188.8.131.52 records the following cluster-level and VM-level features:
- Cluster level: Base , Deduplication, Compression, Stretched Cluster, Data-at-rest Encryption, File Services, HCI Mesh, Shared Witness, Data in Transit Encryption, and Cloud Native Storage. When these features are enabled, the entire cluster is marked as using these features.
- At a VM level, usage is reported per cluster: Raid 5/6 Erasure Coding feature is enabled at the individual virtual machine level but scoped and reported at the cluster level. If one or more virtual machines (regardless of the power state) have enabled this feature, then this feature is considered enabled for the entire cluster. Usage Meter 184.108.40.206 examines the vSAN features enabled for the cluster to determine the reported license edition. The following vSAN features are automatically detected by Usage Meter and reported in the vSAN Cluster History Report.
|Raid 5/6 Erasure Coding
|Deduplication and Compression
|Data in Transit Encryption
|Cloud Native Storage
Note: Usage Meter 220.127.116.11 detects VMs compliant with Storage Policy - Raid 5/6 Erasure Coding. When one or more VMs in a vSAN enabled cluster are compliant with this policy, customers are billed at vSAN Advanced edition.
vSAN Reporting #
vSAN usage is reported as monthly aggregated total used storage capacity by a vSAN license edition in the Monthly Usage Report generated by Usage Insight. More granular information about the vSAN usage can be seen in the vSAN Cluster History Report (see an example below). This report includes information about what storage capacity and features have been used by a cluster per time interval. It also shows the detected vSAN license edition of a cluster. The features that are used by a vSAN cluster can be calculated from the vSANFint column in that report. See the vSAN Cluster History Report information. The average used storage for vSAN is calculated as: Average GB = (Sum of consumed storage capacity in GB per-hourly collections) / (Hours in a month). The value can be zero if no vSAN usage exists or vSAN was not configured. Average Used Storage means the storage capacity consumed by all virtual machine disks (VMDK) and not available for new allocations in GB averaged during the applicable reporting period. This includes swap space (if utilized) and the RAID overhead set within the storage policy.
Note: Usage Meter 18.104.22.168 only reports usage against the vSAN license the detected features are part of. For example, a cluster with a vSAN Enterprise license is detected to use features also part of vSAN Advanced, like Compression and Deduplication. In this case, if there are no other features used that are only part of vSAN Enterprise during the reporting month, then the Monthly Usage Report will report usage against the vSAN Advanced edition. The following vSAN editions are reported in the generated reports by Usage Insight:
- vSAN Standard.
- vSAN Advanced.
- vSAN Enterprise
Note: vSAN is not reported standalone and included in Horizon DaaS bundles. Also, vSAN with Desktop and ROBO licenses are excluded from the usage reports.
vSAN Cluster History Report #
vSAN Cluster History Report contains the used capacity (in MB) per time interval for vSAN enabled clusters in vCenter Servers metered by Usage Meter 22.214.171.124. Additionally, it displays the vSAN license edition and the features used by a cluster. Note: To verify which vSAN cluster features were detected by Usage Meter 126.96.36.199, use the integer value in the table below and compare it with the vsanFInt column in the Cluster History Report.
A vSAN cluster might use several features, and the way to find them is to subtract from the vSANFint value for a cluster the highest possible int value of a vSAN feature detected by Usage Meter.
For example, if you have a value of 6 in the vSANFint column in the cluster history report, subtract 4 (the highest possible value of a vSAN feature that can be subtracted from 6). The int value of 4 represents Compression, as seen from the table below. The result of the subtraction will be 2 (6-4), which stands for Deduplication. In conclusion, the cluster with a vSANFint value of 6 in the vSAN cluster history report uses two vSAN features: Compression and Deduplication.
|Feature Int Value
Sample Cluster History Report and Monthly Usage Report
|vSAN Used (MB**)**
|1 day 00:59:59
In the Cluster History Report, the vSAN license is the edition activated for a cluster and detected by Usage Meter 188.8.131.52. Another important column in the report is vSANFint. With the values in this column, you can identify the features used by a cluster per time interval. The detected features determine the vSAN license edition by which the aggregated usage will be reported in the Monthly Usage Report. There might be a difference between the detected license edition activated for a cluster and the reported license edition in the Monthly Usage Report. This happens when the cluster has used only a portion of the features part of the license. These features are also part of another license, e.g., a cluster with an Enterprise license has only used features that are also part of the vSAN Standard edition. As a result, only what has been used during the reporting period is reported against the respective license edition in the Monthly Usage Report. See below what the Monthly Usage Report will be for the vSAN consumption shown in the above Cluster History Report:
|Unit of Measure
|Units to be Reported
|VMware Virtual SAN Standard
|Avg Billed vSAN Storage (GB)
|VMware Virtual SAN Advanced
|Avg Billed vSAN Storage (GB)
The units reported in the Monthly Usage Report for vSAN are calculated based on the average vSAN storage capacity consumption throughout the month in GB per vSAN license edition, rounded down to the nearest whole number.
Note: The vSAN storage consumption in the Cluster History Report is shown in MB; thus, it must be converted to GB to check if the usage in the Cluster History Report matches that in the Monthly Usage Report.