Virtual Machine Snapshot Usage Analysis - wrong numbers?

Unleash the power of System Center for vSphere and Hyper-V | Veeam Task Manager for Hyper-V

Virtual Machine Snapshot Usage Analysis - wrong numbers?

Veeam Logoby jannep » Thu Apr 27, 2017 12:05 pm

HI!
I started looking at our snapshot alerts and I found that it does not show correct numbers. The alert shows the size of the machine including snapshots. Not only snaphots.

Example:
"The total size (of all snapshots) is 145 408.03 MB. Large snapshots files can rapidly fill up datastore space. Such snapshots also take a long time to commit when finally deleted."

That machine has a disk of 140 000 MB So the snapshot is infact only 5 000 MB (no worries there). Is this a bug in the management pack? It should only look at the snapshot size.
jannep
Novice
 
Posts: 7
Liked: never
Joined: Mon Oct 17, 2016 11:57 am
Full Name: Jan Pettersson

Re: Virtual Machine Snapshot Usage Analysis - wrong numbers?

Veeam Logoby sergey.g » Thu Apr 27, 2017 5:27 pm

Hi Jan,

Could you shere with us screenshot of a datastore browser pointed onto the folder with snapshots for this VM?

VMware will switch and accumulate vmdks for snapshots when you do another one and another one, also there should be a snapshot of memory file, so maybe there is some kind of confusion about what exactly the snapshot is?

Thanks.
sergey.g
Expert
 
Posts: 455
Liked: 75 times
Joined: Wed May 02, 2012 1:49 pm
Full Name: Sergey Goncharenko

Re: Virtual Machine Snapshot Usage Analysis - wrong numbers?

Veeam Logoby jannep » Wed May 17, 2017 11:28 am

There must have been an error with the numbers that day.
Probably the numbers were that high when the alert was triggered but when we checked it had shrunk or created a new snapshot (snapshot was from veeam).
jannep
Novice
 
Posts: 7
Liked: never
Joined: Mon Oct 17, 2016 11:57 am
Full Name: Jan Pettersson

Re: Virtual Machine Snapshot Usage Analysis - wrong numbers?

Veeam Logoby sergey.g » Thu May 18, 2017 2:53 pm

Hi,

Well such huge snapshot for backup purposes could be exactly because this VM already has a snapshot, if it's sitting there for quite some time and VM is actively doing something on the disk, the size of the snapshot could grow significantly and rapidly and because of this pre-existing snapshot Veeam Backup will need more time backing up the VM. Possibly because of all of the above factors, the snapshot size grow even further and you see the alert from Veeam MP.

You can check the following thread in Backup forum on why it's not a best practice to have a snapshot for a VM which should be backed up.
[url]
veeam-backup-replication-f2/how-to-backup-particual-snapshot-state-t13288.html[/url]
sergey.g
Expert
 
Posts: 455
Liked: 75 times
Joined: Wed May 02, 2012 1:49 pm
Full Name: Sergey Goncharenko


Return to Veeam Management Pack for Microsoft System Center



Who is online

Users browsing this forum: No registered users and 1 guest