Description of problem:
Correctly we collect only active stat statistics for vm devices from the dwh_vm_disks_history_view of the engine db.
This view filters data regarding snapshots and templates.
This data , for example "vm_disk_actual_size_mb" , is important if we want to know the total actual used disk size for the vm for that time.
I think that the data we collected in "vm_disk_actual_size_mb" is not really relevant and we should update it to include snapshots and not add another column.
It is only one snapshot out of maybe several. If we dont have snapshots for the vm then this number will correct but if we do then keeping only the size of the current snapshot is meaningless.
Do you agree?
(In reply to Shirly Radco from comment #5)
> I think that the data we collected in "vm_disk_actual_size_mb" is not really
> relevant and we should update it to include snapshots and not add another
> It is only one snapshot out of maybe several. If we dont have snapshots for
> the vm then this number will correct but if we do then keeping only the size
> of the current snapshot is meaningless.
> Do you agree?
I agree. change the value from now on and resync the data, if it's not in a history table.
Could you please provide Fixed in version/Build ID?
Also, for verification is enough to check engine db dwh_vm_disks_history_view before and after snapshot creation if there is a difference in vm_disk_actual_size_mb?
In order to test you will need an env with vms that have snapshots and see that the calculated value of the field is the sum of all snapshots and not only the size of the "Current" snapshot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.