Snapshot storage utilization mismatch between VM snapshot tab and Storage details view in VMware Cloud Director Tenant portal
search cancel

Snapshot storage utilization mismatch between VM snapshot tab and Storage details view in VMware Cloud Director Tenant portal

book

Article ID: 404728

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • This issue is noticed on virtual machines that contains hard disks mapped to two different storage policies.
  • When a snapshot is taken, there is a different in storage size reported between VM snapshots tab and snapshot usage reported under storage details of VM tiles view.

    For example: Refer the following screenshots:

    VM snapshots tab:



    Snapshot usage reported under storage details of VM tiles view:

Environment

VMware Cloud Director 10.6.x

Cause

The VmSnapshotStorageClassMetricsView model correctly identifies the total number of records, However it is unable to deserialize or map those distinct records to their respective model objects.

Resolution

Kindly upgrade to VMware Cloud Director 10.6.1.2 to resolve this issue.

Alternatively, you can verify the actual storage utilization by following the details below:

The snapshot storage size displayed under the VM Snapshots tab reflects the accurate value. This value is calculated as the sum of the current storage usage of the existing VM disks along with certain snapshot configuration files (such as vmsn and vmsd).

  • Memory snapshot: Storage consumed by existing disks (VMDKs) plus memory.
  • Non-memory snapshot: Storage consumed by existing disks (VMDKs) only.
    • Note: Although a VM may be provisioned with a specific capacity, the actual storage consumption depends on how much space is actively used by the disks.

To review the storage consumed by the VMDKs, please follow these steps:

  1. Login vCenter Web client and navigate to datastore where the VM disks reside.
  2. Locate the VM folder and browse the files Using Datastore Browser.
  3. Review the storage consumed by existing vmdk files(not the snapshot disks).
    Example:
  4. Similarly, browse other datastores where the VM disks are placed and review the usage.