Weve used them, not had any issues that i know of..
Although its not something were going lots of..
I know i did 4 or 5 last week, all seemed ok..
I have found the most reliable method of creating and removing snapshots is while the VM is powered off. We have never had timeouts creating snapshots, however, when removing them, we have IF the snapshot has been active for a while.
If you get a timeout while trying to remove a snap, you basically need to wait for the snap to flush. Speed depends on disk and SAN configuration. I agree this is somehwat frustrating, but the fact that snaps basically work is a real lifesaver for our application folks when bringing up rather complicated applications. They have dealt with some of these issues but take them in stride because the feature basically works and has saved their rear-ends a couple of times.
Ohh Yes - we have this one too.
Their is another thread that seems to be regarding this - I have used the disable Sync.driver workaround. We havent been running for long after this change, but it seems to work. The good side is that is apparently no bad side to this workaround.
Not true - creating a snapshot never takes more than 5 secs. Rmoving is a different story, but this is not were the problem is.
Their is another thread that seems to be regarding
this - I have used the disable Sync.driver
workaround. We havent been running for long after
this change, but it seems to work. The good side is
that is apparently no bad side to this workaround.
Are you certain about there not being a side effect to disabling the Sync driver? I just don't want my backups to become unusable.
I don't know if this will help, but about a month ago I had an "operation timed out" message from Virtual Center while trying to commit the snapshot. I was not sure whether the commit operation took place or not so I fired up a post and an SR. Both confirmed that the snapshot commit did actually took place. http://www.vmware.com/community/message.jspa?messageID=554867