vSphere 5.5 and ESXi 5.5

Hi all,

today I am not writing because of a certain problem or thing I stumbled upon. The “news” I want to share is somewhat “old” (26 August 2013), too: VMware announced vSphere 5.5 and ESXi 5.5!

Why am I posting this? Besides some cool new features in Hardware Version 10 or on the VDP side and Hypervisor side, a mayor change that will affect how we use vCenter in our Company is: Full Mac OS X Client integration (including the plugin for vCenter WebClient).

Now, if that isn’t great news? 😉

Here’s a short sheet about whats new: http://blogs.vmware.com/vsphere/files/2013/09/vSphere-5.5-Quick-Reference-0.5.pdf

And heres the long story: http://www.vmware.com/files/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf

All the best,



Execution error: E10056: Restore failed due to existing snapshot. Job Id: (Full Client Path:)

After a while of backing up VMs via vSphere Data Protection (VDP) the backup jobs for four VMs failed. The message said they needed consolidation.

After the consolidation everything started to work for 3 VMs, but not for the fourth. Now I was getting the following error:

Execution error: E10056: Restore failed due to existing snapshot. Job Id: <job-id> (Full Client Path:)

The GUI said nothing about needed consolidation, no snapshots where created, either, and if you look into the VMs config you see that the hdd points to a vmdk, not to a 00001.vmdk snapshot file. So, everything seemed to be in order, right?

After reading some articles I found a vmware KB entry: VDP Backup fails

The solution therein: Old 000001.vmdk-files lying around unused, nowhere referenced or anything. Simply deleting them will help (but an additional move to another location is recommended just to be on the save side).

So with this everything is up and running again! Thanks vmware!

vSphere Data Protection 5.1: Backup fails for Windows Server 2008 R2 VMs

So today I got to the bottom of another interesting case concerning backups with vSphere Data Protection.

After deploying the virtual appliance, registering it to the vSphere Server and creating backup jobs, something interesting happened: Linux VMs got backed up, whereas Server 2008 R2 VMs got errors.

To make a long story short: It has to do with the UUIDs of the virtual HardDisks and Windows VSS, and the fix is quite easy, as can be seen in this KB from VMware:


vmware: no snapshot in snapshot manager, but *0000002.vmdk still around?

I ran into this problem a few days ago when I tried to give a vm a little more storage. I could not, it was greyed out. After looking into it I found the problem: This virtual machine was running on a snapshot. So, go to the snapshot manager and find: nothing!

Tracking the problem back: A while ago the vm needed a snapshot in order to be safe for an update. So, create snapshot, install updates. All fine. After that, the snapshot was deleted, and in the snapshot manager you did not see any snapshots.

But somehow the vms config still pointed to the delta-file instead of the original. And the delta was still growing. All in all over a 100GB, because this has been going on for quite some time now.

With vSphere 5 / ESXi5 there is a quick solution. In the virtual machines tab look for “Needs consolidation”. It is says yes, right click the vm -> snapshots -> consolidate.

But here we have ESXi 4.1 and vSphere 4.1, so no “consolidate” nor “needs consolidation”. How to fix this?

It can be done in most cases quite easily, but I needed some encouragement from others that already performed this: Create a new snapshot, and right when it is done: Delete all.

This will consolidate even the not shown snapshots and leave you with an all functioning vm.

So, for me, that did the trick. But sometimes it is not so easy. Please consider reading these links first:





Wish you the best of luck with your problem, and please read my disclaimer 😉