Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Total storage used by Snapshots do not match the storage data in Virtualization Manager

Total storage used by Snapshots do not match the storage data in Virtualization Manager

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 702 Votes: 0 Revisions: 8

Issue

When viewing trends, the Total Storage Used by Snapshots displayed does not match the storage data in Virtualization Manager reports.

Cause

This is a known issue in 5.0.x that is related to how snapshots are numbered by VMware. This is expected behavior when deleting snapshots out of sequence or from the earliest to latest snapshot. A similar issue exists in pre-5.0.x releases which has been mostly addressed in 5.0.x releases.

Virtualization Manager uses a combination of VMSN and VMDK files to calculate the snapshot total storage in trends. VMSN files record the exact state of the VM.  VMDK files are the virtual hard drive for the VM. When you create a snapshot, the snapshot number is recorded as part of the VMSN and VMDK file names, however numbering for each file type is different. When you delete a snapshot, you can introduce differences to the numbering that result in this mismatch.

The following table illustrates how numbering differences occur.

Action

VMSN #

VMDK #

Create snapshot 1

1

1

Create snapshot 2

2

2

Delete snapshot 1

-

-

Create snapshot 3

1

3

If you deleted the latest snapshot, the numbers will match, as in the next table.

Action

VMSN #

VMDK #

Create snapshot 1

1

1

Create snapshot 2

2

2

Delete snapshot 2

-

-

Create snapshot 3

2

2

The storage data from the reports come from the VMDK files. The difference between trends and reports are generally negligible, until a snapshot numbering mismatch occurs.

 

Last modified

Tags

Classifications

Public