The Datastore Capacity dashboard highlights the datastores that need attention. This dashboard is designed for the Capacity team and not for the Operations team. It provides a long term and a top-down view, enabling the Capacity team to plan the future expansion and refresh of the aging hardware technology. The Datastore Capacity dashboard is designed for both the VMware administrator and the Storage administrator to foster closer collaboration between the two teams.
See Capacity Dashboards for common design consideration among all the dashboards for capacity management.
Wastage is displayed by a new color. Dark gray indicates wastage as capacity is not used. The performance problem due to low utilization can be caused by a bottleneck elsewhere.
How to Use the Dashboard
The Datastore Capacity dashboard is layered, gradually providing details as you work top-down in the dashboard.
- The Shared Datastores by Capacity Remaining and Shared Datastores by Time Remaining bar charts summarize the clusters based on capacity remaining and time remaining. Just because you are running low on capacity does not mean you are running out of time.
- The two bar charts work together. The ideal situation is low capacity remaining and high time remaining. This means that your resources are cost effective and are working as expected.
- There are three heat maps, the primary heat map being Remaining Capacity.
- The other two heat maps Used Capacity by Datacenter and Used Capacity by Datastore Cluster, cover used capacity. The Used Capacity by Datastore Cluster heat map is designed for datastore clusters.
- If you use Datastore Cluster as your standard, replace the grouping with it. This widget is sorted by the least capacity remaining.
- The Disk Space widget displays the total capacity allocated and the actual capacity used. You can compare the total Capacity vs the Provisioned capacity vs the Used capacity. If the allocated space increases and the actual capacity does not, then it means that the VMs have not been used. You can ensure that you do not run out of space sooner than expected.
- In the VM Count widget, a rising number that is not complemented by a similar rise in the used space indicates a latent demand.
- There are three reclamation opportunities: powered off VM, snapshot, and orphaned VMDK.
- The snapshot must be 0 GB. If it is not 0, then it should be temporary. A snapshot lasting beyond a day must be investigated.
- Orphaned VMDK are the ones that are not associated with any VM. The orphaned VMDK must be 0.
Points to Note
Storage in VMware IaaS is presented as a datastore. In a large environment, group datastores as datastore clusters for ease of operations. vSAN uses datastores to present its storage, but it requires a different formula for capacity and performance management. In certain situations, RDM (Raw Device Mapping) and network file shares are also used by certain VMs.