Virtualization Manager Reports > Datastore Detail
  
Version 9.2.01
Datastore Detail
Detail reports are related to a specific enterprise object, such as a backup job or SAN fabric. You can only access detail reports through a link presented in the context of a main report, providing additional information that augments the main report. Detail reports cannot be generated, customized, or saved, as they are specific to the report from which they were derived. Therefore, they will not be available in search results.
Use Quick search to find the main template, report or a dashboard by name. Search is case insensitive, supports partial entries, and will display a list of potential matches.
As you enter the template, dashboard or report name in the Quick Search field, up to 10 potential matches are displayed. If the result is shown, you can select and run it directly from the match list. You can also select All Items to display the full search results page and further filter your results.
You can use the Explorer tab to browse through the StorageConsole templates, dashboards and reports. The navigation pane displays templates organized by products along with user created, and system folders. The main report is located here:
Click a Datastore name.
Name
Name of the datastore.
Type
Datastore type: a specific NFS file system or NAS.
Server
This field is related to Datastore type and will be populated only when the type is NAS.
Folder
The VM folder in which this Datastore is located. This field is related to Datastore type and will be populated only when the type is NAS.
Multiple Host Access
Indicates if this datastore can be shared by multiple hosts: Yes or No.
Last Updated
Timestamp of the last write access.
VMDK Max File Size
The capacity of a virtual disk from the point of view of a virtual machine.
# VMs
This number links to the VM Summary report, listing the VMs associated with this Datastore.
# Extents
The number of extents that were added to expand the datastore (up to 32 physical storage extents).
# Disks
The number of physical disks associated with the datastore.
# Arrays
The number of arrays from which this datastore gets physical storage links to Array Capacity & Utilization.
VMDK Used
The sum of all virtual disks - VMDK (.vmdk files). This sum does not include snapshot metadata files, however, other outdated snapshot data may be in vmdk files. For this reason, VMDK Used may exceed VM Disk Capacity, the amount that was configured when the VM was created.
Total VM Used
Size of the virtual machine, which includes VMDK files, log files, and snapshots; the sum of all the files taking up storage by this VM. This value links to the VM Files Summary report, which lists the usage details. For details about data collection options that impact these values, see Virtualization Manager Data Collection Options and Datastore Utilization.
Is Thin
Indicates whether or not the datastore supports thin provisioning on a per file basis. When thin provisioning is used, backing storage is lazily allocated.
This is supported by VMFS3. VMFS2 always allocates storage eagerly. Thus, this value is false for VMFS2. Most NAS systems always use thin provisioning. They do not support configuring this on a per file basis, so for NAS systems this value is also false.
Total Capacity
Total capacity of this Datastore.
Free Capacity
Available capacity in this Datastore
Used Capacity
Amount of this Datastore’s capacity already in use
Capacity Usage
Mouse over this thermometer to view the usage percentage
VM Disk Capacity
This is the amount of storage that was configured and presented to the Guest OS when the virtual disk was originally created for the VM. When you connect to a VM client, this capacity appears as hard disks. The VM disk capacity values included the size of all VMDKs, excluding snapshots.
VM Not In Inventory
Indicates VMs that are not currently in the inventory, but are taking up space in the Datastore. These are VMs that are not visible in VMware vCenter. Click this link to view the VM Files Summary. This value will be zero if data collection is configured to collect data from only datastores associated with VMs in the inventory. For details about data collection options that impact these values, see Virtualization Manager Data Collection Options and Datastore Utilization.
Over Provisioned
Indicates what percentage is over-provisioned. This helps you in evaluating possible virtual environment expansions.
Datastore Detail: Datastore Usage Breakdown
See Physical Disk Detail.
Datastore Capacity & Forecast
Extents
Name
Name of the storage device with the following 4-part name:
HBA, SCSI target, SCSI LUN, disk partition
EXAMPLE: vmhba1:1:3:1

If vmhba appears in the name, it indicates a specific physical HBA on the ESX server.

If the fourth segment is not included in the name, it indicates that the datastore has consumed the whole disk/LUN.
Type
VMFS or NFS
Mode
physical, logical
Capacity
Capacity of this particular extent
Disk
The disk on which the extent resides
Array
If there is a LUN mapping, a link to the corresponding array accesses the Array Capacity and Utilization report.
Shared VM Servers
For a description of the fields in this table, see VM Server Summary.
VM Utilization
For a description of these fields, see VM Summary.
Virtualization Manager Data Collection Options and Datastore Details
A Virtualization Manager data collection policy can be configured to gather data as follows:
• Inventory (default option): Collect only the data associated with the VMs in the inventory.
• Collect all files in datastore: Perform a full scan of the datastore to discover files that are resident on the datastore, but not associated with a VM in the inventory. This option finds files that may be invisible to VMware, but that are consuming space on the datastore.
 
 
When the Inventory option is configured in the data collector policy, it has the following impact on fields shown in this report:
• Non-VM Files and VM Not In Inventory will be zero.
• Total VM Used will be reduced by the amount that would have been collected as VM Not In Inventory if an all files collection had been done.
• VMDK and Other VM Files values typically will not be impacted by the datastore collection type.