- Posts: 1
- Liked: never
- Joined: Dec 03, 2009 11:32 pm
- Full Name: Jason Gagui
Easiest solution is to up the notification thresholds...but was wondering if anyone out there has come accross this and/or has a fix?
Thanks in advance,
- SVP, Product Management
- Posts: 24421
- Liked: 3403 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
I recommend that you investigate VM log file. During the final snapshot commit, ESX stuns the VM completely in order to commit the data into VMDK, and logs the stun time in the VM log file. You may want to check these numbers, and if they seem to large, check with VMware if this is "normal". I have never seen stun lasting longer than 2 sec in my lab when I did ESX4 snapshots stress testing (such as committing snapshots while copying lots of data to VM at the same time).
One thing that may really make everything crawl is concurrent snapshot operations on the same LUN (which causes SCSI reservation conflicts).
Users browsing this forum: Google [Bot] and 37 guests