Good troubleshooting. To find the source of the problem you will need to keep ruling things out.

Thus far you have ruled out the provisioning type of the VM (which should not matter if you are using basic compression) and the backup target disks.

Can you request a trial license and setup a fresh install of vBackup 4.0.2 on a different machine? Make sure you install VMware Virtual Disk Development Kit (VDDK) 5.1.4 and 5.5.4 and use VMware Virtual Disk Manager from VDDK 5.5.4.

You should also use a different network cable and connection for the "test" backup server so that this can be ruled out as well. If there is any way you can connect the test backup server into the same network switch as the host server's management port this might be helpful.

Also, you might verify that you have 1Gb network connectivity on each connection between the backup server and the management port on the host server.

Please let us know.

A couple of reasons for installing VDDK 5.1.4 and VDDK 5.5.4:

1) VDDK 5.1.4 is provided in an MS Installer package and will create all of the required registry keys for you. VDDK 5.5.4 is only provided in ZIP format and requires that you manually create the registry keys yourself.

2) VDDK 5.1.4 includes the compiled VMware Disk Mount utility. VDDK 5.5.4 does not.


Installation Instructions:

1) Install VDDK 5.1.4 using all of the default settings. VDDK 5.1.4 will install to C:\Program Files (x86)\VMware\Virtual Disk Development Kit.

2) Unzip VDDK 5.1.4 to C:\Temp\VMware-vix-disklib-5.5.4-2454786.x86_64, then copy C:\Temp\VMware-vix-disklib-5.5.4-2454786.x86_64 to C:\Program Files.

3) Once you have vBackup installed set the "VMware Virtual Disk Manager Application Directory" setting to: "C:\Program Files\VMware\VMware-vix-disklib-5.5.4-2454786.x86_64\bin", uncheck "Use same application directory for VMware Disk Mount" and set the "VMware Disk Mount Application Directory" setting to: "C:\Program Files (x86)\VMware\VMware Virtual Disk Development Kit\bin".