@Dennis , thanks for the post!

Can you take a look at the vsbkp.log on the proxy and see what we see?  Also, let me know what transport mode you are using.

One possibility is a lock that is held during the HOTADD mount of the guest vm disk during backup due to this the backup failed.

Try setting the transport mode to ‘auto’ if it isn’t.

Most likely explanation is that you are using hotadd transport and the storage controller on the VM is set to IDE or something like that. Hotadd requires SCSI type disks but usually you can’t just change it on the VM since the operating system may freak out.

Auto should detect that the VM is not eligible for HotAdd or SAN transport and try NBD backup mode - assuming you have allowed port 902 open from the VSA proxy to the ESXi server where the VM is running.

Hi,
thanks. Log from the relevant VM is at the attachment.
Transport Mode is AUTO. Used is SAN.

Thanks
Dennis
 

Hi Dennis,

Looking at that logs, we see the following error:
15456 7650  03/23 23:15:06 3484480 CVMWareInfo::_MountVM_VCB4() - Failed to parse disk name: :vmware_win_03] 4ce59828-79ae-46ec-96ff-d0d41b9a4b77.vmdk

To me it looks like the referenced VMDK, is in the root of the Datastore. - I’d suggest moving VM Disks into the VM Folder and checking the results of another backup.

Alternatively, you could vMotion the VM to another DS and check the results.

Let us know how you get on.

Best Regards,

Michael

Bingo, Storage vMotion solved the problem.
Many thanks.